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 2222461

Summary: CentOS Stream 9 installer sometimes can't secure boot
Product: Red Hat Enterprise Linux 9 Reporter: Richard Finicky <shiny.key5737>
Component: shimAssignee: Bootloader engineering team <bootloader-eng-team>
Status: CLOSED MIGRATED QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, carl, jwboyer, mharri
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-16 19:44:11 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:
Attachments:
Description Flags
secure boot error message none

Description Richard Finicky 2023-07-12 21:14:37 UTC
Created attachment 1975481 [details]
secure boot error message

I want to try out Stream 9 and install it on a spare computer. Unfortunately,
There's a secure boot error: Invalid Signature Detected.

The SHA256 sum of the iso matches what's on the CentOS website. If secure boot
is disabled, the "Test this media" option in the grub menu passes.

This error doesn't happen on the same computer with the Debian 12 or Alma 9.2
installers.

I've tried booting a few other computers to compare and the results are mixed:

CentOS Stream 9 20230704.1 /w secure boot enabled

ASUS All-in-One (Ryzen 7 5700U): Error

ASUS Zenbook (Core i7-1165G7): Error

HP T730 (AMD RX-427BB): Boots, but the installer is unusable b/c of screwed up graphics

HP TE01 (Core i7-12700F): OK

HP TE01 (Core i7-13700): Error

Lenovo S540 (Core i5-10210U): OK

Minisforum em680 (Ryzen 7 6800U): Error

Debian 12 is OK for all of the above
Alma 9.2 is OK as well, except for the HP T730

Comment 1 Brian Stinson 2023-07-12 22:07:03 UTC
We're working on updating the Shim package in Stream 9. I suspect that may take care of this, but I'll report back here when that's done.

Comment 2 RHEL Program Management 2023-09-16 19:43:20 UTC
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.

Comment 3 RHEL Program Management 2023-09-16 19:44:11 UTC
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.