Description of problem: During upgrade, ocm-o reports `Progressing=False` even though the daemonset for the controller is still upgrading and the latest version is not being reported. Version-Release number of selected component (if applicable): 4.4.0 How reproducible: Sometimes Expected results: The operator should report `Progressing=True` until the daemonset rollout has completed. Additional info: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1484/pull-ci-openshift-machine-config-operator-master-e2e-gcp-upgrade/1098
Verified in version: 4.5.0-0.nightly-2020-03-06-190457 STEPS: 1. Update build.config.openshift.io, check when 3 pods are not all running in openshift-controller-manager project, then ocm-o report "Progressing=True" $ oc get co -w |grep openshift-controller-manager openshift-controller-manager 4.5.0-0.nightly-2020-03-06-190457 True True False 131m openshift-controller-manager 4.5.0-0.nightly-2020-03-06-190457 True True False 131m openshift-controller-manager 4.5.0-0.nightly-2020-03-06-190457 True False False 132m
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.5 image release advisory), 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-2020:2409