Bug 1863033

Summary:	the baremetal-operator does not track changes to host's boot mode
Product:	OpenShift Container Platform	Reporter:	Doug Hellmann <dhellmann>
Component:	Bare Metal Hardware Provisioning	Assignee:	Doug Hellmann <dhellmann>
Bare Metal Hardware Provisioning sub component:	baremetal-operator	QA Contact:	Polina Rabinovich <prabinov>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	beth.white, rbartal, zbitter
Version:	4.6	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 16:22:35 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 Doug Hellmann 2020-08-03 14:01:03 UTC

Description of problem:

If the user changes the bootMode between inspection and deployment, the new value is not used.

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


How reproducible:

always

Steps to Reproduce:
1. create a host with a boot mode
2. wait for inspection to complete
3. change the boot mode
4. deploy an image to the host

Actual results:

the host may fail to boot if the mode is incorrect

Expected results:

the most recent user input for boot mode is used for provisioning

Additional info:

Comment 1 Doug Hellmann 2020-08-03 14:02:02 UTC

https://github.com/metal3-io/baremetal-operator/pull/612 is the upstream fix

Comment 2 Doug Hellmann 2020-09-03 18:32:01 UTC

https://github.com/openshift/baremetal-operator/pull/95 brings the fix downstream.

Comment 7 errata-xmlrpc 2020-10-27 16:22:35 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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196