ARM64 images don't boot when secureboot is enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* This is a backport to focal and bionic of arm64 secureboot enablement work that has already been released in jammy.
* Users wishing to use secureboot to boot ARM64 bionic and focal cloud images will fail. This is due to the bionic and focal images including incorrect grub EFI binaries. The correct grub EFI binaries, that are included in jammy arm64 cloud images are `shim-signed` and `grub-efi-
[Test Plan]
* Create bionic and focal arm64 images using the updated livecd-rootfs
* Test that both bionic and focal arm64 images boot successfully on a cloud platform that requires secureboot
* Test that non-secureboot functionality has not regressed by testing that both bionic and focal images successfully boot on a cloud platform where secureboot is not required
[Where problems could occur]
* A lot of different derivative images inherit from `disk-image-
has the potential to tamper with the arcane matters related to boot
[Other Info]
* This is a backport, images of Jammy and newer have had those changes since release
* There is an SRU exception for livecd-rootfs described here: https:/
description: | updated |
Changed in livecd-rootfs (Ubuntu Impish): | |
status: | New → Fix Released |
description: | updated |
description: | updated |
description: | updated |
Marked the bug to reflect the status of each series. What about Impish?