** Changed in: grub2 (Ubuntu Yakkety)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
overwritten.
Status in curtin:
Confirmed
Status in MAAS:
Fix Committed
Status in MAAS 2.2 series:
Triaged
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2 source package in Trusty:
Triaged
Status in grub2 source package in Xenial:
Triaged
Status in grub2 source package in Yakkety:
Won't Fix
Bug description:
[Impact]
Typically when you install Ubuntu on an EFI system, it installs a new default
EFI boot entry that makes the system reboot directly into the OS. During MAAS
installs, curtin is careful to disable that behavior. MAAS requires the default
boot entry to remain PXE, so that it can direct the system to boot from disk or
network as necessary. curtin does this by passing --no-nvram to grub-install
when installing the bootloader.
*Update*: newer curtin releases actually allow the creation of a new
boot entry, but updates the boot menu to make PXE the default. That
change is orthogonal to this bug.
***However***, this doesn't stop a new default boot entry from being
added after deploy. If the user installs a grub package update or
manually runs 'grub-install', booting from disk will become the
default, and MAAS will lose control of the system.
[Proposed Solution (er... glorified workaround)]
The GRUB package in zesty now has support for setting the --no-nvram flag
*persistently*. This is implemented via a debconf template
(grub2/update_nvram). If curtin sets this flag to "false" during install,
post-deploy grub updates will also pass the --no-nvram flag when running
grub-install.
This isn't a perfect solution - users can still call grub-install
manually and omit this flag.
[Test Case]
- MAAS deploy an EFI system.
- After deploy, login and run 'sudo apt --reinstall install grub-efi-$(dpkg
--print-architecture)
- Reboot and observe that the system does not PXE boot.
[Regression Risk]
- The GRUB implementation does not change the defaults of the package. The
user would need to opt-in to the "grub2/update_nvram=false". This option is
also only presented to users who specifically request a low debconf priority
(e.g. expert mode installs).
- XXX curtin risk XXX
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
