We're really close to 4.11 GA, and this is a 4.10 issue, not a new-in-4.11 issue, so I'm punting it out to 4.11.z.
Verifying it before PR is merged. 1. Launch a cluster using cluster-bot 2. Change the upstream to a dummy cincy # oc adm upgrade --include-not-recommended Cluster version is 4.11.0-0.ci.test-2022-08-08-034233-ci-ln-6sy9vft-latest Upstream: https://storage.googleapis.com/ocp-ota-1659938683/graph-1659938684 Channel: buggy Recommended updates: VERSION IMAGE 4.99.999999 registry.ci.openshift.org/ocp/release@sha256:9999999999999999999999999999999999999999999999999999999999999999 Supported but not recommended updates: Version: 4.88.888888 Image: registry.ci.openshift.org/ocp/release@sha256:8888888888888888888888888888888888888888888888888888888888888888 Recommended: False Reason: ReleaseIsRejected Message: Too many CI failures on this release, so do not update to it https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/releasestream/4.10.0-0.nightly/release/4.10.0-0.nightly-2021-11-24-075634 Version: 4.77.777777 Image: registry.ci.openshift.org/ocp/release@sha256:7777777777777777777777777777777777777777777777777777777777777777 Recommended: False Reason: SomeInvokerThing Message: On clusters on default invoker user, this imaginary bug can happen. https://bug.example.com/a All the updates are resolved successfully. CVO seems not to get stuck.
Based on comment#2, moving it to verified state.
We're considering a 4.10.z backport in [1]. [1]: https://issues.redhat.com//browse/OCPBUGS-235
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 (Moderate: OpenShift Container Platform 4.11.1 bug fix and security 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/RHSA-2022:6103