Bug 1976009

Summary:	GrubPXE boot works as expected at the first time, after that, it's not able to find the local UEFI partition
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Provisioning	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	dgupte, inecas, lzap, rlavi, sganar, sshtein
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Waldirio M Pinheiro 2021-06-25 00:07:19 UTC

Description of problem:
The customer with some Gen10 blades started facing some issues when using Grub via PXE, in the first boot everything was working as expected. However, after restarting the blade, when loading the local Grub was not possible to find the local UEFI partition.

When turning the blade off and redoing the process, at the first boot everything was ok but restarting the same behavior was happening again and again.

This behavior was noticed only on Gen10, the customer has some Gen9 and Gen8 but they were working as expected.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Blades restarting all the time after the first restart

Expected results:
after loading the PXE Grub, loading the local UEFI partition and booting via local disk.

Additional info:

Comment 6 Brad Buckingham 2023-07-21 21:06:39 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.