> 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 from. Right now that
is <server>/grub/grub.cfg. That file attempts to chainload
<server>/grub/grub.cfg-${net_default_mac} and if that fails
<server>/grub/grub.cfg-default-amd64. MAAS could also respond to
<server>/grub/grub.cfg-$uuid as we have that information as well. Having
grub do that automatically would remove a request and a level of
chainloading.
https://git.launchpad.net/maas/tree/src/provisioningserver/boot/uefi_amd64.py
--
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:
https://bugs.launchpad.net/maas/+bug/1879012/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
