Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1913047

Summary:	baremetal clusteroperator progressing status toggles between true and false when cluster is in a steady state
Product:	OpenShift Container Platform	Reporter:	Doug Hellmann <dhellmann>
Component:	Bare Metal Hardware Provisioning	Assignee:	Beth White <beth.white>
Bare Metal Hardware Provisioning sub component:	cluster-baremetal-operator	QA Contact:	Polina Rabinovich <prabinov>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, prabinov, sdasu, stbenjam
Version:	4.7	Keywords:	Triaged, UpcomingSprint
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:50:15 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 2021-01-05 19:58:04 UTC

Description of problem:

The "baremetal" ClusterOperator "progressing" field toggles between true and false continuously, even while the cluster is in a steady state.


Version-Release number of selected component (if applicable): 4.7.0-0.nightly-2021-01-04-153716


How reproducible: always


Steps to Reproduce:
1. run `oc get clusteroperator baremetal` in a loop at the shell prompt
2.
3.

Actual results:

$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-04-153716   True        True          False      23h
$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-04-153716   True        True          False      23h
$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-04-153716   True        False         False      23h
$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-04-153716   True        False         False      23h


Expected results:

The "progressing" column should always say "False".

Additional info:

Comment 2 Polina Rabinovich 2021-01-19 09:50:12 UTC

The "progressing" column always with "False" status.

[kni@provisionhost-0-0 ~]$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-18-144603   True        False         False      13h
[kni@provisionhost-0-0 ~]$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-18-144603   True        False         False      13h
[kni@provisionhost-0-0 ~]$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-18-144603   True        False         False      13h
[kni@provisionhost-0-0 ~]$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-18-144603   True        False         False      13h
[kni@provisionhost-0-0 ~]$ oc get clusteroperator baremetal
NAME        VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
baremetal   4.7.0-0.nightly-2021-01-18-144603   True        False         False      13h

Comment 5 errata-xmlrpc 2021-02-24 15:50:15 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633