Bug 2011824

Summary:	Baremetal Cluster Operator Not Available when Provisioning Deleted
Product:	OpenShift Container Platform	Reporter:	Adina Wolff <awolff>
Component:	Bare Metal Hardware Provisioning	Assignee:	sdasu
Bare Metal Hardware Provisioning sub component:	cluster-baremetal-operator	QA Contact:	Amit Ugol <augol>
Status:	CLOSED NEXTRELEASE	Docs Contact:
Severity:	low
Priority:	low	CC:	aos-bugs, bfournie, mstaeble, sdasu
Version:	4.8	Keywords:	Triaged, UpcomingSprint
Target Milestone:	---
Target Release:	4.9.z
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-04 21:37:20 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:	1991641
Bug Blocks:

Description Adina Wolff 2021-10-07 13:29:52 UTC

Version:

4.8

Platform:

baremetal

Please specify:
IPI

What happened?

After deleting provisioning CR, baremetal cluster operator shows 'available = false'
The discussiong about bz1991641 led to the conclusion that this is not the expected behavior.

[kni@provisionhost-0-0 ~]$ oc delete provisioning provisioning-configuration
provisioning.metal3.io "provisioning-configuration" deleted
[kni@provisionhost-0-0 ~]$ oc get clusteroperator|grep bare
baremetal                                  4.8.0-0.nightly-2021-08-05-031749   False       False         False      14s
[kni@provisionhost-0-0 ~]$ 
 
What did you expect to happen?

baremetal cluster operator remains available: 

[kni@provisionhost-0-0 ~]$ oc get clusteroperator|grep bare
baremetal                                  4.9.0-0.nightly-2021-08-07-175228   True        False         False      26h     
[kni@provisionhost-0-0 ~]$
How to reproduce it (as minimally and precisely as possible)?

Comment 2 sdasu 2022-01-04 21:37:20 UTC

This has been fixed in 4.10 and there is no need to change the message displayed by the "baremetal" CO in a 4.9 z-release.