Description of problem: The cco clusteroperator does not set a level gate which allows the CVO to incorrectly believe it has been upgraded even if it fails. Version-Release number of selected component (if applicable): 4.1.4 Steps to Reproduce: 1. oc adm release extract --to=/tmp/folder quay.io/openshift-release-dev/ocp-release:4.1.4 2. edit 0000_50_cloud-credential-operator_10_cluster-operator.yaml and notice it does not have the level gate present in, for example, 0000_50_cluster-monitoring-operator_05-clusteroperator.yaml status: versions: - name: operator version: "4.1.4" Actual results: Without this level gate, the CVO can pass by the operator during the upgrade even if the operator fails to upgrade. Additional info: Urgency at request of ccoleman. release info should include: status: versions: - name: operator version: "0.0.1-snapshot"
https://github.com/openshift/cloud-credential-operator/pull/81
Has merged, setting ON_QA and target release 4.2. Will clone for 4.1.z.
Verified with "oc adm release extract --to=/tmp/folder registry.svc.ci.openshift.org/origin/release:4.2" Result: [cloud-user@preserve-qe-olnester-ocp-workstation folder]$ cat 0000_50_cloud-credential-operator_10_cluster-operator.yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: name: cloud-credential status: versions: - name: operator version: "4.2.0-0.okd-2019-07-08-162751"
I believe this fix was reverted in https://github.com/openshift/cloud-credential-operator/pull/90 -- please let me know if I misunderstood, otherwise we'll want to drop this bug from the 4.1.6 advisory.
That still works for 4.2 apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: name: cloud-credential status: versions: - name: operator version: "4.2.0-0.okd-2019-07-16-062255"
Sorry, I failed to notice that this is the 4.2 bug. The revert was for 4.1. Thanks for looking.
*** Bug 1737420 has been marked as a duplicate of this bug. ***
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