Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2070997

Summary: Kernel 5.14.0-76.el9.x86_64 and 5.14.0-75.el9.x86_64 won't boot
Product: Red Hat Enterprise Linux 9 Reporter: Adam Miller <admiller>
Component: kernelAssignee: core-kernel-bot <core-kernel-mgr>
kernel sub component: Kernel-Core QA Contact: Red Hat Kernel QE team <kernel-qe>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: bstinson, jwboyer, ptalbert, rharwood
Version: CentOS StreamFlags: pm-rhel: mirror+
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-01 19:19:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Miller 2022-04-01 14:23:07 UTC
Description of problem:

Can't boot, get following menu to screen when attempting to:

error: ../../grub-core/kern/efi/sb.c:150:bad shim signature.
error: ..../grub-core/loader/i386/efi/linux.c:208:you need to load the kernel first.
Press any key to continue..

Version-Release number of selected component (if applicable):
5.14.0-76.el9.x86_64 and 5.14.0-75.el9.x86_64 

How reproducible:
Always


Steps to Reproduce:
1. dnf update
2. reboot
3.

Actual results:
https://photos.app.goo.gl/zSYfBTwxgCiwBf9GA


Expected results:
A booting system

Additional info:
The last working kernel is kernel-5.14.0-71.el9.x86_64

Comment 1 Brian Stinson 2022-04-01 17:20:29 UTC
@rharwood It looks like kernel -71 -72 -73 and -74 are signed properly in CentOS Stream, but after that the kernels are signed with the Test cert:

• pesign -l --in=vmlinuz                                      
---------------------------------------------
certificate address is 0x7f1b2bff3808
Content was not encrypted.
Content is detached; signature cannot be verified.
The signer's common name is Red Hat Test Certificate
No signer email address.
Signing time: Wed Mar 30, 2022
There were certs or crls included.
---------------------------------------------


Did this update to pesign cause any changes here? https://kojihub.stream.rdu2.redhat.com/koji/buildinfo?buildID=17784


Kernel -74 (signed properly): https://kojihub.stream.rdu2.redhat.com/koji/buildinfo?buildID=17731
Kernel -75 (signed with the test cert): https://kojihub.stream.rdu2.redhat.com/koji/buildinfo?buildID=17791

Comment 2 Robbie Harwood 2022-04-01 19:19:54 UTC

*** This bug has been marked as a duplicate of bug 2070940 ***