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:
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
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