Bug 2138019
Summary: | kernel-5.14.0-17X.el9.x86_64 / Not bootable (EFI) after Firmware update | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Leon Fauster <leonfauster> |
Component: | distribution | Assignee: | Brian Stinson <bstinson> |
Status: | CLOSED MIGRATED | QA Contact: | Brian Stinson <bstinson> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | CentOS Stream | CC: | bstinson, cglombek, coxu, francisco123321, jwboyer, mharri, slewsys, travier |
Target Milestone: | rc | Keywords: | MigratedToJIRA |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kernel-5.14.0-183.el9 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-14 13:26:29 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
Leon Fauster
2022-10-26 21:56:28 UTC
TLDR: /boot/vmlinuz-5.14.0-16* versus /boot/vmlinuz-5.14.0-17* shows The signer's common name is CentOS Secure Boot Signing 201 versus The signer's common name is Red Hat Test Certificate ############################################################ # ls -1 /boot/vmlinuz-5.14.0-16* |xargs -n1 pesign --show-signature -i --------------------------------------------- certificate address is 0x7fba079ec0e8 Content was not encrypted. Content is detached; signature cannot be verified. The signer's common name is CentOS Secure Boot Signing 201 The signer's email address is security Signing time: Thu Sep 22, 2022 There were certs or crls included. --------------------------------------------- --------------------------------------------- certificate address is 0x7f7ce4d0bd28 Content was not encrypted. Content is detached; signature cannot be verified. The signer's common name is CentOS Secure Boot Signing 201 The signer's email address is security Signing time: Fri Sep 23, 2022 There were certs or crls included. --------------------------------------------- # ls -1 /boot/vmlinuz-5.14.0-17* |xargs -n1 pesign --show-signature -i --------------------------------------------- certificate address is 0x7efe96b739c8 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: Sat Oct 01, 2022 There were certs or crls included. --------------------------------------------- --------------------------------------------- certificate address is 0x7f65df7ed9c8 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: Fri Oct 07, 2022 There were certs or crls included. --------------------------------------------- --------------------------------------------- certificate address is 0x7fe45a19e728 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 Oct 12, 2022 There were certs or crls included. --------------------------------------------- --------------------------------------------- certificate address is 0x7fd435357ee8 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: Mon Oct 17, 2022 There were certs or crls included. --------------------------------------------- # rpm -q kernel|sort kernel-5.14.0-167.el9.x86_64 kernel-5.14.0-168.el9.x86_64 kernel-5.14.0-171.el9.x86_64 kernel-5.14.0-174.el9.x86_64 kernel-5.14.0-176.el9.x86_64 kernel-5.14.0-177.el9.x86_64 We had a misconfiguration on our kernel signing builders that we think caused this. We have reapplied the proper configuration which will be picked up on the next kernel build. Great, that the cause was found. My firmware update was then just a coincidence ... *** Bug 2138077 has been marked as a duplicate of this bug. *** *** Bug 2136892 has been marked as a duplicate of this bug. *** *** Bug 2135315 has been marked as a duplicate of this bug. *** Looks like it's working for us with kernel-5.14.0-183.el9.x86_64 so I think this can be closed / moved to QA now. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |