Bug 2011824 - Baremetal Cluster Operator Not Available when Provisioning Deleted
Summary: Baremetal Cluster Operator Not Available when Provisioning Deleted
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.8
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: ---
: 4.9.z
Assignee: sdasu
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On: 1991641
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-07 13:29 UTC by Adina Wolff
Modified: 2022-01-04 21:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-04 21:37:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1991641 1 medium CLOSED Baremetal Cluster Operator still Available After Delete Provisioning 2022-03-12 04:37:46 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.