ClusterOperator status.versions must always be set in the payload otherwise it will trigger the fallback mode for the CVO which is not good. More details: https://coreos.slack.com/archives/CCH60A77E/p1554743050139700
Fixed by https://github.com/openshift/cluster-dns-operator/pull/92
upgraded from 4.1.0-0.nightly-2019-05-04-210601 to 4.1.0-0.nightly-2019-05-05-070156 and verified ### before upgrade $ oc get clusteroperator/dns -o yaml <---skip---> versions: - name: operator version: 4.1.0-0.nightly-2019-05-04-210601 - name: coredns version: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3f2209f60c556962fa4bcf681ea3996bb47cb2f7ae18a4129d20827b71238b13 - name: openshift-cli version: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:32251dc3229be24b7c011403052388fe41dc821eb63078d3513e9b20c2ed0b4e ### post upgrade versions: - name: operator version: 4.1.0-0.nightly-2019-05-05-070156 - name: coredns version: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3f2209f60c556962fa4bcf681ea3996bb47cb2f7ae18a4129d20827b71238b13 - name: openshift-cli version: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8989f12b58aeaef17fd840d7471c208b1b7fc107000af9f03a4190ae325c46e7
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, 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-2019:0758