[Bug 1912830] [NEW] Use non-removable uefi bootloader in cloud-images by default

Dimitri John Ledkov 1912830 at bugs.launchpad.net
Fri Jan 22 18:15:12 UTC 2021


Public bug reported:

[Impact]

 * use non --removable uefi installation for cloud-images

 * Currently cloud-images use --removable grub installation, which makes
the disk images look at lot more like our installer .isos, than
installed systems.

   This causes many issues:

 * ubuntu efiboot entry is not created by the fallback manager from shim
 * one cannot reorder ubuntu boot entry, and/or boot and apply fwupdate updates (if possible)
 * measurements are unstable, and change if one call grub-install and or upgrades things
 * often grub & shim upgrades are not applied at all as \EFI\ubuntu does not exist on the ESP

 * We should switch to only shipping shim/fallback/mm in \ESP\Boot and
ship \ESP\ubuntu on the cloud-image ESPs such that we regain stable
measurements; ubuntu boot entry; and upgrades of grub and shim.

[Test Case]

 * After UEFI firstboot $ efibootmgr --verbose => should contain
`ubuntu` entry pointing at ESP\ubuntu\shim*.efi binary, which should be
added to the bootorder

[Where problems could occur]

 * Existing systems which were booted from previous style images, will
not upgrade shim|grub on the ESP, and must call `grub-install` or `grub-
multi-install` to correct that.

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  Use non-removable uefi bootloader in cloud-images by default

Status in livecd-rootfs package in Ubuntu:
  New

Bug description:
  [Impact]

   * use non --removable uefi installation for cloud-images

   * Currently cloud-images use --removable grub installation, which
  makes the disk images look at lot more like our installer .isos, than
  installed systems.

     This causes many issues:

   * ubuntu efiboot entry is not created by the fallback manager from shim
   * one cannot reorder ubuntu boot entry, and/or boot and apply fwupdate updates (if possible)
   * measurements are unstable, and change if one call grub-install and or upgrades things
   * often grub & shim upgrades are not applied at all as \EFI\ubuntu does not exist on the ESP

   * We should switch to only shipping shim/fallback/mm in \ESP\Boot and
  ship \ESP\ubuntu on the cloud-image ESPs such that we regain stable
  measurements; ubuntu boot entry; and upgrades of grub and shim.

  [Test Case]

   * After UEFI firstboot $ efibootmgr --verbose => should contain
  `ubuntu` entry pointing at ESP\ubuntu\shim*.efi binary, which should
  be added to the bootorder

  [Where problems could occur]

   * Existing systems which were booted from previous style images, will
  not upgrade shim|grub on the ESP, and must call `grub-install` or
  `grub-multi-install` to correct that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912830/+subscriptions



More information about the foundations-bugs mailing list