https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.1-to-4.2/10 > Jul 02 07:22:10.566 E clusterversion/version changed Failing to True: ClusterOperatorNotAvailable: Cluster operator machine-config is still updating
https://github.com/openshift/machine-config-operator/pull/910
This is a 4.1.x -> 4.2 issue so testing should be spin up a 4.1 cluster and upgrade it to 4.2
The PR above had a bug, this one fully takes care of the bug: https://github.com/openshift/machine-config-operator/pull/913
Notes for testing: - install 4.1.x - grab any 4.2 nightly or payload that includes the above PRs - run an upgrade The above results in a success upgrade (tested myself manually)
Verified upgrading from 4.1.7 to 4.2.0-0.nightly-2019-07-30-073644 ``` $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.7 True False 8s Cluster version is 4.1.7 $ oc patch clusterversion/version --patch '{"spec":{"upstream":"https://openshift-release.svc.ci.openshift.org/graph"}}' --type=merge clusterversion.config.openshift.io/version patched $ oc adm upgrade --force --to-image=registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-07-30-073644 Updating to release image registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-07-30-073644 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.7 True True 1s Working towards registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-07-30-073644: downloading update $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.7 True True 5m53s Working towards 4.2.0-0.nightly-2019-07-30-073644: 24% complete $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.7 True True 10m Working towards 4.2.0-0.nightly-2019-07-30-073644: 83% complete $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-07-30-073644 True False 16h Cluster version is 4.2.0-0.nightly-2019-07-30-073644 ```
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:2922