[Bug 1792575] Re: Boot failure with efi shims from 20180913.0

[Brian Murray]

Hello Peter, or anyone else affected,

Accepted shim-signed into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.33.1~16.04.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: shim-signed (Ubuntu Xenial)
       Status: Confirmed => Fix Committed

** Tags removed: verification-done-xenial
** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim in Ubuntu.
https://bugs.launchpad.net/bugs/1792575

Title:
  Boot failure with efi shims from 20180913.0

Status in MAAS:
  Invalid
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Invalid
Status in shim-signed package in Ubuntu:
  Invalid
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Invalid
Status in shim-signed source package in Xenial:
  Fix Committed
Status in grub2 source package in Bionic:
  Fix Released
Status in grub2-signed source package in Bionic:
  Fix Released
Status in shim source package in Bionic:
  Invalid
Status in shim-signed source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Chainloading grub via grub in a netboot context using MAAS's Boot to local disk feature.

  [Test cases]
  1) Deploy UEFI system using MAAS
  2) After deployment, have the system reboot to local disk (via netboot).

  [Regression potential]
  It is possible that the changes to chainloading logic that evaluates the sizes for various sections of code that gets copied to memory to load the next bootloader might fail to correctly evaluate the sections, or otherwise copy sections incorrectly, but this regression scenario is indistinguishable from the current case, there the system fails to load the next bootloader anyway. Error messages may vary, but the net result for a regression would be an incorrectly loaded bootloader, and thus error messages at boot from grub.

  ---

  We have had several nodes that had been deployed on Sept. 12 and were
  booting correctly fail to boot.

  On the console and during tracing we could see they were getting dhcp
  and pxe information, but then errored out with "relocation failed",
  dropping into a fallback grub menu with a Local boot option.

  After copying over bootx64.efi grubx64.efi from
  https://images.maas.io/ephemeral-v3/daily/bootloaders/uefi/amd64/20180906.0/
  instead of 20180913.0/ and rebooting, boot would commence
  successfully.

  Hardware: Dell R640
  maas 2.3.5-6511-gf466fdb-0ubuntu1~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1792575/+subscriptions