On Mon, Jul 31, 2017 at 12:07 PM, Ryan Harper <[email protected]> wrote: > On Fri, Jun 30, 2017 at 3:06 PM, Blake Rouse <[email protected]> > wrote: > >> I think having MAAS tell curtin to set the grub2/update_nvram to False, >> works fine. Since the path to the EFI loader should not change this is >> acceptable. >> >> Having grub adjust the EFI vars because of an upgrade is really bad in >> MAAS case because a following re-deploy will no longer work. >> > > We currently have a config key: > > grub: > update_nvram: <boolean: default False> > > Which tells curtin whether or not to pass the --no-nvram flag to > grub-install > > We could also set the grub2/update_nvram debconf value to match this config. > Will that achieve the desired goal?
If grub2/update_nvram is always false, then yes. But if it were set to true, that would regress this issue. > Is there a use-case for a separate value used during grub-install than from > what one would put in the debconf value? AIUI, curtin now *does* update NVRAM at install, but then reorders the boot entries after the fact to keep PXE booting as the default. I'm not sure if this is related to the config key or not. Even so, we would still want update_nvram to be set to false after install, to avoid grub updates from overriding the PXE boot default. -dann -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642298 Title: UEFI Xenial install sets computer to boot from hard disk To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
