Is this issue reproducible on MAAS 3.3+?
** Changed in: maas
Status: Triaged => Incomplete
** Changed in: maas
Milestone: 3.5.0 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi folks,
It looks like the issue is still around - I just got hit by this with
MAAS 3.1.0 on Focal. However, replacing grubx64.efi with the one from
/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed made the trick and I
was able to boot without any manual intervention.
Can we consider
https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu40/+build/21017796/+files
/grub-efi-amd64-bin_2.04-1ubuntu40_amd64.deb
from this, you can extract
/usr/lib/grub/x86_64-efi/monolithic/grubnetx64.efi and drop it into
/var/snap/maas/common/maas/boot-
** Changed in: maas
Milestone: 2.9.2 => 2.9.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications about
** Changed in: maas
Milestone: 2.9.0b7 => 2.9.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications
** Changed in: maas
Milestone: 2.9.0b4 => 2.9.0b7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications
** Tags added: fr-683
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications about this bug go to:
** Changed in: maas
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications
** Changed in: maas
Milestone: 2.9.0b2 => 2.9.0b3
** Changed in: maas
Milestone: 2.9.0b3 => 2.9.0b4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up
nevermind, uuid is the one from dhcp client-id obviously as implemented
/ referenced in my earlier comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up
I mean the output of /sys/class/dmi/id/product_uuid. However I'm not
sure how reliable that is. Since I made that comment we've had multiple
users report(LP:1893690) some vendors are handing out duplicate UUIDs.
MAAS handles this by ignoring any UUID which has been duplicated.
--
You received
"MAAS could also respond to /grub/grub.cfg-$uuid as we have that
information as well"
In that sentence which $uuid do you mean? UUID of the machine? Something
grub can query from smbios?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: maas
Milestone: 2.9.0b1 => 2.9.0b2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
> Not sure if we want a feature to automatically scan/find grub.cfg on
remote host by ip/mac/uuid/etc:
Currently MAAS only specifies the path to the bootloader, not the
bootloader config. It expects the bootloader will automatically request
the config from where the bootloader was downloaded
So the SUSE srpm has a lot interesting patches that implement:
* configuring networking from EFI
- bootp bootpv6
- dhcp dhcpv4
- static, v4 & v6, with/without port numbers
- http https file access via EFI protocol
I don't believe any of that is upstream, and/or only partially, But i
** Tags added: maas-grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications about this bug go to:
** Changed in: maas
Milestone: 2.8.0 => 2.9.0b1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications
** Changed in: maas
Milestone: 2.8.0rc3 => 2.8.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications
So I managed to make it work by using SUSE's grubx64.efi instead.
Steps are basically:
- Replace bootx64.efi with the OpenSUSE one
- Write a grub.cfg shim at the root which does "configfile
(http,172.17.16.10:5248)/grub/grub.cfg-default-amd64"
Reboot and everything works as expected.
OpenSUSE
FYI, reproduced this in LXD virtual machines trying to use UEFI HTTPBOOT.
Similar setup, http-only (no https yet) and no secureboot enabled.
Shim and grub are both retrieved properly over http, then dumped into a
grub shell without it ever attempting to download grub.cfg over the
network.
** Changed in: maas
Milestone: 2.8.0rc1 => 2.8.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications
Please provide remote artifacts:
All bootloader files are pulled from the Bionic archive and provided on
images.maas.io by lp:maas-images. bootloaders.yaml[1] describes what files are
pulled from what packages. You can download the tars at[2]
Please provide local artifacts:
The local artifacts
Need additional information as per
https://bugs.launchpad.net/maas/+bug/1865515/comments/16
** Changed in: shim-signed (Ubuntu)
Status: New => Incomplete
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
"I modified MAAS to only provide GRUB and skip the Shim" => that will
not work in secureboot without canonical CA certificates provisioned. If
only MS certificate is provisioned (default for most x86 hw) then one
must use shim too.
--
You received this bug notification because you are a member
** Package changed: grub (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012
Title:
GRUB does not bring up networking when loaded over HTTP
To manage notifications
I modified MAAS to only provide GRUB and skip the Shim. In that case
HTTP boot still doesn't work. It looks like when GRUB is loaded over
HTTP it does not bring up networking. I can still manually load
networking with net_dhcp and specify the remote grub.cfg file. GRUB does
download the kernel and
28 matches
Mail list logo
