2022v1 signed cd-boot-images (grub 2.06-2ubuntu{16,14.1}, shim 15.7-0ubuntu1)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cd-boot-images-amd64 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
cd-boot-images-arm64 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
cd-boot-images-ppc64el (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
cd-boot-images-riscv64 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Installer doesn't boot when old stuff is revoked.
The -riscv64 and -ppc64el packages are more no-change-rebuilds to make sure we're building with the latest bits. amd64/arm64 are a bit more important, but I'm attaching them to the same bug as they're all part of our usual point-release refreshes.
[Test plan]
Testing is done for the grub and shim uploads on their own, and we'll get ISO testing but only after it's released, so for proposed really no testing necessary, just check it builds and ends up with the right binaries.
[Release schedule]
This needs to be released after the kernels used on the image are released. block-proposed tags have been set accordingly.
[Where problems could occur]
The new shim or grub may fail to boot on some systems of course due to the changes in memory management or the other upstream shim changes between 15.4 and 15.7.
And well we gotta release in the right order to get bootable images, see Release Schedule above.
summary: |
- Block proposed + 2022v1 signed cd-boot-images |
description: | updated |
summary: |
- 2022v1 signed cd-boot-images + 2022v1 signed cd-boot-images (grub 2.06-2ubuntu16, shim 15.7-0ubuntu1) |
summary: |
- 2022v1 signed cd-boot-images (grub 2.06-2ubuntu16, shim 15.7-0ubuntu1) + 2022v1 signed cd-boot-images (grub 2.06-2ubuntu16/14.1, shim + 15.7-0ubuntu1) |
summary: |
- 2022v1 signed cd-boot-images (grub 2.06-2ubuntu16/14.1, shim + 2022v1 signed cd-boot-images (grub 2.06-2ubuntu{16,14.1}, shim 15.7-0ubuntu1) |
description: | updated |
tags: | added: block-proposed-jammy |
Changed in cd-boot-images-amd64 (Ubuntu Jammy): | |
milestone: | none → ubuntu-22.04.2 |
Changed in cd-boot-images-arm64 (Ubuntu Jammy): | |
milestone: | none → ubuntu-22.04.2 |
Changed in cd-boot-images-ppc64el (Ubuntu Jammy): | |
milestone: | none → ubuntu-22.04.2 |
Changed in cd-boot-images-riscv64 (Ubuntu Jammy): | |
milestone: | none → ubuntu-22.04.2 |
Hello Julian, or anyone else affected,
Accepted cd-boot- images- amd64 into jammy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ cd-boot- images- amd64/20. 1 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, what testing has been performed on the package and change the tag from verification- needed- jammy to verification- done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- jammy. 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/ PerformingSRUVe rification . 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.