Bug 1936844

Summary:	4.7 Backport - CAPBM changes to support flexible reboot modes
Product:	OpenShift Container Platform	Reporter:	Rhys Oxenham <roxenham>
Component:	Bare Metal Hardware Provisioning	Assignee:	Rhys Oxenham <roxenham>
Bare Metal Hardware Provisioning sub component:	baremetal-operator	QA Contact:	Shelly Miron <smiron>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	derekh, smiron
Version:	4.7	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.7.z
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Adds capabilities to the CAPBM to request a hard power off upon remediation, leveraging the recent changes to the baremetal-operator to support new reboot modes. Reason: The baremetal-operator recently got extended to support flexible reboot modes, either hard or soft. The default mode is a soft reboot, but for remediation purposes we want this to be hard to recover workloads as quickly as possible. Result: CAPBM requests hard reboot when remediation is required, bypassing the default soft power-off that the baremetal-operator issues.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-12 23:22:56 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:
Bug Depends On:	1937122
Bug Blocks:

Description Rhys Oxenham 2021-03-09 10:55:23 UTC

Description of problem:

This is a Bugzilla entry to track the 4.7 backport of the CAPBM changes to support the new BMO code that allows a hard reboot to be requested by clients. In this case, for remediation purposes we want the CAPBM to set the mode=hard annotation; this code was recently merged in 4.8.

This work is split into two components-

1) The BMO changes to support the reboot mode

2) The CAPBM changes to apply the hard reboot mode for remediation purposes

Additional info:

PR that pulled the BMO changes into 4.8
https://github.com/openshift/baremetal-operator/pull/128
https://bugzilla.redhat.com/show_bug.cgi?id=1927678

PR for backporting above BMO changes into 4.7
https://github.com/openshift/baremetal-operator/pull/130
https://bugzilla.redhat.com/show_bug.cgi?id=1936407

PR that pulled the CAPBM changes into 4.8
https://github.com/openshift/cluster-api-provider-baremetal/pull/138

PR for backporting above CAPBM changes into 4.7
https://github.com/openshift/cluster-api-provider-baremetal/pull/144

This Bugzilla will be marked as dependant on 1936407 (the BMO changes need to land before the CAPBM).

Comment 6 errata-xmlrpc 2021-04-12 23:22:56 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.7.6 bug fix 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/RHBA-2021:1075