On Wed, Aug 2, 2017 at 9:49 AM, Ryan Harper <email address hidden>
wrote:

> On Wed, Aug 2, 2017 at 8:12 AM, Blake Rouse <email address hidden>
> wrote:
>
> > update_nvram is now default for curtin and re-ordering is also default
> >
>
> MAAS send update_nvram as True ? or False by default?
>

MAAS sends nothing. The default is True, so MAAS uses the default.


>
>
> > for UEFI installs. I don't think setting grub2/update_nvram in debconf
> > should be a default. To me MAAS should tell curtin to set that debconf
> > as that is overriding a package default.
> >
>
> OK, do we want to re-use the update_nvram curtin config to *ALSO* set the
> debconf value? Or do we need to be able to send/set those values
> independently?
>

You could re-use it but that would mean by default curtin would always set
that for an installed system. By default having curtin update the nvram on
install makes since, even using subiquity. But overriding the packing of
grub of the installed system is more of a MAAS specific case to me, so I
would think it should be its own setting, that MAAS must explicitly set to
True.


>
>
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > 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
> >
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1642298
>
> Title:
>   UEFI Xenial install sets computer to boot from hard disk
>
> Status in curtin:
>   Confirmed
> Status in MAAS:
>   Invalid
> 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:
>   Triaged
>
> 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
>