> If you edit the default opsrcs are disable in cvo for 4.1 then the upgrading to 4.2 will also last a long time and won't be finish until delete the "override" part. We encounter this issue again. It blocks the cluster upgrading. Is it as expected? mac:~ jianzhang$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-10-07-161806 True True 39m Unable to apply 4.2.0-0.nightly-2019-10-07-203748: the cluster operator marketplace has not yet successfully rolled out mac:~ jianzhang$ oc get clusterversion version -o yaml apiVersion: config.openshift.io/v1 kind: ClusterVersion metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"config.openshift.io/v1","kind":"ClusterVersion","metadata":{"annotations":{},"name":"version"},"spec":{"overrides":[{"group":"","kind":"OperatorSource","name":"redhat-operators","namespace":"openshift-marketplace","unmanaged":true},{"group":"","kind":"Deployment","name":"marketplace-operator","namespace":"openshift-marketplace","unmanaged":true}]}} creationTimestamp: "2019-10-08T01:03:24Z" generation: 5 name: version resourceVersion: "192548" selfLink: /apis/config.openshift.io/v1/clusterversions/version uid: 6d8ea7fe-e967-11e9-90ea-fa163e6db328 spec: channel: stable-4.2 clusterID: ae487f96-c419-4672-b8bb-6646e26d3e40 desiredUpdate: force: true image: registry.svc.ci.openshift.org/ocp/release@sha256:4bb7f6a0467e844c65f4e1eb17fc322c90f7af02497124186840e87e048c9644 version: 4.2.0-0.nightly-2019-10-07-203748 overrides: - group: "" kind: OperatorSource name: redhat-operators namespace: openshift-marketplace unmanaged: true - group: "" kind: Deployment name: marketplace-operator namespace: openshift-marketplace unmanaged: true upstream: https://openshift-release.svc.ci.openshift.org/graph status: availableUpdates: null conditions: - lastTransitionTime: "2019-10-08T01:19:31Z" message: Done applying 4.2.0-0.nightly-2019-10-07-161806 status: "True" type: Available - lastTransitionTime: "2019-10-08T07:53:15Z" message: Cluster operator marketplace is still updating reason: ClusterOperatorNotAvailable status: "True" type: Failing - lastTransitionTime: "2019-10-08T07:33:34Z" message: 'Unable to apply 4.2.0-0.nightly-2019-10-07-203748: the cluster operator marketplace has not yet successfully rolled out' reason: ClusterOperatorNotAvailable status: "True" type: Progressing - lastTransitionTime: "2019-10-08T05:52:28Z" status: "True" type: RetrievedUpdates desired: force: true image: registry.svc.ci.openshift.org/ocp/release@sha256:4bb7f6a0467e844c65f4e1eb17fc322c90f7af02497124186840e87e048c9644 version: 4.2.0-0.nightly-2019-10-07-203748 history: - completionTime: null image: registry.svc.ci.openshift.org/ocp/release@sha256:4bb7f6a0467e844c65f4e1eb17fc322c90f7af02497124186840e87e048c9644 startedTime: "2019-10-08T07:33:34Z" state: Partial verified: false version: 4.2.0-0.nightly-2019-10-07-203748 - completionTime: "2019-10-08T07:33:34Z" image: registry.svc.ci.openshift.org/ocp/release@sha256:7bb10cbfeff324b751a58c31143ff98ce781ec829dfb070faca4e396e20478b5 startedTime: "2019-10-08T01:03:41Z" state: Completed verified: false version: 4.2.0-0.nightly-2019-10-07-161806 observedGeneration: 5 versionHash: He_PHMpprcU= mac:~ jianzhang$ oc get deployment NAME READY UP-TO-DATE AVAILABLE AGE certified-operators 1/1 1 1 7h12m community-operators 1/1 1 1 7h12m marketplace-operator 1/1 1 1 7h18m redhat-operators 1/1 1 1 50m simplecsc 1/1 1 1 116m mac:~ jianzhang$ oc get operatorsource NAME TYPE ENDPOINT REGISTRY DISPLAYNAME PUBLISHER STATUS MESSAGE AGE certified-operators appregistry https://quay.io/cnr certified-operators Certified Operators Red Hat Succeeded The object has been successfully reconciled 7h13m community-operators appregistry https://quay.io/cnr community-operators Community Operators Red Hat Succeeded The object has been successfully reconciled 7h13m redhat-operators appregistry https://quay.io/cnr redhat-operators Red Hat Operators Red Hat Succeeded The object has been successfully reconciled 51m
Split comment 2 into bug 1759868 for better tracing.
test result: 1.disable all the default opsrcs 2.upgrade cluster twice 4.3.0-0.nightly-2019-10-31-003134 -> 4.3.0-0.nightly-2019-10-31-032443 4.3.0-0.nightly-2019-10-31-003134 -> 4.3.0-0.nightly-2019-10-31-050543 3.update the cluster success.
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-2020:0062