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

[Mathieu Trudel-Lapierre]

Verification-done with the xenial grub2/grub2-signed versions:

$ dpkg -l grub\* | grep ii
ii  grub-common           2.02~beta2-36ubuntu3.20         amd64        GRand Unified Bootloader (common files)
ii  grub-efi-amd64        2.02~beta2-36ubuntu3.20         amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii  grub-efi-amd64-bin    2.02~beta2-36ubuntu3.20         amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 binaries)
ii  grub-efi-amd64-signed 1.66.20+2.02~beta2-36ubuntu3.20 amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)
ii  grub2-common          2.02~beta2-36ubuntu3.20         amd64        GRand Unified Bootloader (common files for version 2)


I am unable to accurately verify chainloading grub bootloaders from network to disk (especially as it appeared to be a hardware-dependent issue), however, I can easily verify the other side-effect of this, which would break chainloading Windows from grub. I was able to chainload Windows 10 just fine with the patches applied.

Given that this is the same two patches as applied in other releases
that was applied without changes, and that they have also successfully
passed validation for both chainloading Windows 10 and chainloading grub
in Peter's environment (comment #21), I find this acceptable testing.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-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 Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in shim source package in Xenial:
  Invalid
Status in shim-signed source package in Xenial:
  Confirmed
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