2022v1 signed cd-boot-images (grub 2.06-2ubuntu{16,14.1}, shim 15.7-0ubuntu1)

Bug #2004164 reported by Julian Andres Klode
10
This bug affects 1 person
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)
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

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/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 cd-boot-images-amd64 (Ubuntu Jammy):
status: New → Fix Committed
tags: added: verification-needed verification-needed-jammy
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Julian, or anyone else affected,

Accepted cd-boot-images-riscv64 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cd-boot-images-riscv64/5.2 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/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 cd-boot-images-riscv64 (Ubuntu Jammy):
status: New → Fix Committed
Changed in cd-boot-images-ppc64el (Ubuntu Jammy):
status: New → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Julian, or anyone else affected,

Accepted cd-boot-images-ppc64el into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cd-boot-images-ppc64el/13.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/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.

tags: added: block-proposed-jammy
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

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.2 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/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 cd-boot-images-arm64 (Ubuntu Jammy):
status: New → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Julian, or anyone else affected,

Accepted cd-boot-images-arm64 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cd-boot-images-arm64/16.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/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 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
Revision history for this message
Steve Langasek (vorlon) wrote :

kernels signed with the correct key have been released to jammy-updates and jammy-security. Unblocking for jammy.

tags: removed: block-proposed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cd-boot-images-amd64 - 20.2

---------------
cd-boot-images-amd64 (20.2) jammy; urgency=medium

  * Add a check that we are not revoked

cd-boot-images-amd64 (20.1) jammy; urgency=medium

  * Rebuild against
    - grub 1.187.3~22.04.1+2.06-2ubuntu14.1
    - shim 1.51.3+15.7-0ubuntu1
    (LP: #2004164)

 -- Julian Andres Klode <email address hidden> Wed, 08 Feb 2023 15:44:15 +0100

Changed in cd-boot-images-amd64 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cd-boot-images-arm64 - 16.1

---------------
cd-boot-images-arm64 (16.1) jammy; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * Rebuild against
    - grub 1.187.3~22.04.1+2.06-2ubuntu14.1
    - shim 1.51.3+15.7-0ubuntu1
    (LP: #2004164)

  [ Julian Andres Klode ]
  * Check that we are not revoked

 -- Julian Andres Klode <email address hidden> Wed, 08 Feb 2023 15:59:18 +0100

Changed in cd-boot-images-arm64 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cd-boot-images-ppc64el - 13.1

---------------
cd-boot-images-ppc64el (13.1) jammy; urgency=medium

  * Rebuild against grub2 2.06-2ubuntu7.2 (LP: #2004164).

 -- Łukasz 'sil2100' Zemczak <email address hidden> Mon, 06 Feb 2023 16:23:41 +0100

Changed in cd-boot-images-ppc64el (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cd-boot-images-riscv64 - 5.2

---------------
cd-boot-images-riscv64 (5.2) jammy; urgency=medium

  * Rebuild against latest grub2 and u-boot (LP: #2004164).

 -- Łukasz 'sil2100' Zemczak <email address hidden> Mon, 06 Feb 2023 17:25:27 +0100

Changed in cd-boot-images-riscv64 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

linux-signed has migrated, so we no longer need to block this in lunar-proposed.

Changed in cd-boot-images-amd64 (Ubuntu):
status: New → Fix Released
Changed in cd-boot-images-riscv64 (Ubuntu):
status: New → Fix Released
Changed in cd-boot-images-ppc64el (Ubuntu):
status: New → Fix Released
Changed in cd-boot-images-arm64 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.