Bug 2091030

Summary:	Some BM may fail booting with default bootMode strategy
Product:	OpenShift Container Platform	Reporter:	Rastislav Wagner <rawagner>
Component:	Console Metal3 Plugin	Assignee:	Rastislav Wagner <rawagner>
Status:	CLOSED ERRATA	QA Contact:	Yanping Zhang <yanpzhan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.10
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Missing option in UI to set boot mode strategy Consequence: UI always used the default (UEFI) boot strategy which caused problems booting up some types of bare metals. Fix: Expose a new field in Add Bare Metal host form to choose appropriate boot mode strategy Result: Bare metal machine can be booted	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:14:45 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 Rastislav Wagner 2022-05-27 11:35:35 UTC

Description of problem:
metal3 allows setting UEFI/UEFISecureBoot and Legacy boot mode strategies. The UI does not expose this option which in some cases leads to not being able to boot the BM .

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

How reproducible:
always

Comment 2 Yanping Zhang 2022-06-01 08:25:45 UTC

Launch a 4.11 Edge cluster, bridge the console frontend with the fix code. 
Check on the bridged console. Go to Compute->Bare Metal Hosts page, click "Add Host"->"New with Dialog", on the creation wizard, there is "Boot mode" field with default value "UEFI", input necessary info, click "Create", check the created BMH yaml, the spec.bootMode is set to "UEFI".  Add MBH with creation wizard, try "UEFISecureBoot" and "Legacy" individually, and check the create BMH yaml, the spec.bootMode is set correctly.

Comment 4 errata-xmlrpc 2022-08-10 11:14:45 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069