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: | kernel | Assignee: | 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 Stream | ||
| 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
@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 *** This bug has been marked as a duplicate of bug 2070940 *** |