Bug 2162629

Summary:	shimx64-centos.efi blocks fwmgr update
Product:	Red Hat Enterprise Linux 8	Reporter:	Pascal Dupuis <cdemills>
Component:	shim	Assignee:	Bootloader engineering team <bootloader-eng-team>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bootloader-eng-team, bstinson, jwboyer, mbenatto
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	rharwood: needinfo? (bstinson)
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 18:16:18 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 Pascal Dupuis 2023-01-20 09:06:24 UTC

Description of problem:
On a multi-OS computer, the presence of /boot/efi/EFI/centos/shimx64-centos.efi blocks the use of fwupdmgr update from Fedora 37

Version-Release number of selected component (if applicable): shim-x64-15-15.el8_2.x86_64


How reproducible: always


Steps to Reproduce:
1. boot to fedora 37
2. fwupdmgr upgrade
3.

Actual results:
Blocked executable in the ESP, ensure grub and shim are up to date: /mnt/CentOS_8/boot/efi/EFI/centos/shimx64-centos.efi Authenticode checksum [cb994b400590b66cbf55fc663555caf0d4f1ce267464d0452c2361e05ee1cd50] is present in dbx

Expected results:

update should be applied

Additional info:

Comment 1 Robbie Harwood 2023-01-24 20:50:11 UTC

shim in RHEL-8 is shim-15.6-1.el8 which is fine from a DBX perspective.

Looks like stream has desynced?  Brian, any thoughts here?

Comment 4 RHEL Program Management 2023-09-16 18:15:55 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 5 RHEL Program Management 2023-09-16 18:16:18 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.