Bug 1830235

Summary:	UEFI boot loop: System BootOrder not found.
Product:	Red Hat Enterprise Linux 8	Reporter:	Laurent G. <defwxyz>
Component:	shim	Assignee:	Bootloader engineering team <bootloader-eng-team>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.2
Target Milestone:	rc
Target Release:	8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-01 07:27:01 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 Laurent G. 2020-05-01 09:02:17 UTC

Description of problem:

I tested Red Hat Enterprise Linux 8.2 beta. After the installation process finished "sucessfully", the laptop can not reboot as it enter an infinite loop.
 
My laptop : DMI: Hewlett-Packard HP EliteBook 850 G2/2216.

It is the same bug as in 1515897

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Install RHEL 8.2 Beta
2.Reboot
3.

Actual results:
Infinite loop with message:
"System BootOrder not found. Initializing defaults. Creating boot entry "Boot005B" with label "Red Hat Enterprise Linux" for file "\EFI\redhat\shim64.efi"

"Reset System"



Expected results:
I expect to see the grub menu with boot entry and the system to start normally.

Additional info:

Comment 1 Laurent G. 2020-05-30 08:39:11 UTC

There is a workaround that works on OpenSuse Tumbleweed. With this Operating System the installation works and also there is a notice that something is not as expected the system is successfully installed and can boot properly.

This is not the case with Red Hat Enterprise Linux 8.2 Beta on that particular PC Laptop.

Comment 4 RHEL Program Management 2021-11-01 07:27:01 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.