*** Bug 2055310 has been marked as a duplicate of this bug. ***
Performing PR pre-merge verification as below: 1. Launch a cluster by using cluster-bot launch openshift/cluster-version-operator#742 gcp # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.ci.test-2022-02-28-055004-ci-ln-3dsr0jb-latest True False 11m Cluster version is 4.9.0-0.ci.test-2022-02-28-055004-ci-ln-3dsr0jb-latest 2. Prepare a dummy cincinnati graph json { "nodes": [ { "version": "4.9.0-0.ci.test-2022-02-28-055004-ci-ln-3dsr0jb-latest", "payload": "registry.build01.ci.openshift.org/ci-ln-3dsr0jb/release@sha256:43b670ce26a460ef6e46c63741694fcafb046fbf3111fb7ef1fefdd1dd39efe4", "metadata": { "io.openshift.upgrades.graph.release.channels": "channel-a,channel-b" } }, { "version": "4.10.0-rc.5", "payload": "registry.ci.openshift.org/ocp/release@sha256:5ebccbbcbeeb3987f9ee3fa7f593c5e24bdd89efd9c6b2e6d525346e4a235ced", "metadata": { "io.openshift.upgrades.graph.release.channels": "channel-a,channel-b" } } ], "edges": [ [0,1] ] } 3. Patch to update upstream and desired update at the same time #oc patch clusterversion version --type json -p '[{"op": "add", "path": "/spec/upstream", "value": "https://raw.githubusercontent.com/shellyyang1989/upgrade-cincy/master/cincy3.json"}, {"op": "add", "path": "/spec/channel", "value": "channel-a"}, {"op": "add", "path": "/spec/desiredUpdate", "value": {"version": "4.10.0-rc.5"}}]' clusterversion.config.openshift.io/version patched 4. Check cv # oc get clusterversion -oyaml apiVersion: v1 items: - apiVersion: config.openshift.io/v1 kind: ClusterVersion metadata: creationTimestamp: "2022-02-28T05:57:30Z" generation: 3 name: version resourceVersion: "30810" uid: 15eab731-07d1-49e3-86b2-3160a8fd2c2a spec: channel: channel-a clusterID: 34184194-03b9-4c50-8aca-14f53eb0562b desiredUpdate: version: 4.10.0-rc.5 upstream: https://raw.githubusercontent.com/shellyyang1989/upgrade-cincy/master/cincy3.json status: availableUpdates: - channels: - channel-a - channel-b image: registry.ci.openshift.org/ocp/release@sha256:5ebccbbcbeeb3987f9ee3fa7f593c5e24bdd89efd9c6b2e6d525346e4a235ced version: 4.10.0-rc.5 conditions: - lastTransitionTime: "2022-02-28T06:38:22Z" status: "True" type: RetrievedUpdates - lastTransitionTime: "2022-02-28T06:18:30Z" message: Done applying 4.9.0-0.ci.test-2022-02-28-055004-ci-ln-3dsr0jb-latest status: "True" type: Available - lastTransitionTime: "2022-02-28T06:18:30Z" status: "False" type: Failing - lastTransitionTime: "2022-02-28T06:38:22Z" message: 'Working towards 4.10.0-rc.5: downloading update' reason: DownloadingUpdate status: "True" type: Progressing desired: channels: - channel-a - channel-b image: registry.ci.openshift.org/ocp/release@sha256:5ebccbbcbeeb3987f9ee3fa7f593c5e24bdd89efd9c6b2e6d525346e4a235ced version: 4.10.0-rc.5 history: - completionTime: null image: registry.ci.openshift.org/ocp/release@sha256:5ebccbbcbeeb3987f9ee3fa7f593c5e24bdd89efd9c6b2e6d525346e4a235ced startedTime: "2022-02-28T06:38:22Z" state: Partial verified: false version: 4.10.0-rc.5 - completionTime: "2022-02-28T06:18:30Z" image: registry.build01.ci.openshift.org/ci-ln-3dsr0jb/release@sha256:43b670ce26a460ef6e46c63741694fcafb046fbf3111fb7ef1fefdd1dd39efe4 startedTime: "2022-02-28T05:57:30Z" state: Completed verified: false version: 4.9.0-0.ci.test-2022-02-28-055004-ci-ln-3dsr0jb-latest observedGeneration: 3 versionHash: 4thv-EgawMk= kind: List metadata: resourceVersion: "" selfLink: "" 5. Check upgrade status # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-rc.5 True False 10m Cluster version is 4.10.0-rc.5 The upgrade is not blocked by invalid version.
Hello @lmohanty, a follow-up with this BZ tatus. Looks like this PR is close to merge. Just need /cherry-pick-approved label! Not sure who should add that label? We desire this fix in CVO 4.9 to support OCP 4.9 to 4.10 upgrade for our Telco RAN solution.
Hello @lmohanty, a follow-up with this BZ status. Looks like this PR is close to merge. Just need /cherry-pick-approved label! Not sure who should add that label? We desire this fix in CVO 4.9 to support OCP 4.9 to 4.10 upgrade for our Telco RAN solution.
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.9.24 bug fix 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/RHBA-2022:0798