Hide Forgot
Description of problem: The Marketplace Operator does not update it's clusteroperator to correctly portray the status of the operator. Issues include: 1. The clusteroperator progress condition is never set to True. This condition should be set to display when a new version of the operator is being rolled out. When the operator has finishes deploying, the progress condition should be set to false and the Available/Failing conditions should be updated to reflect the state of the operator. Currently, the clusterOperator always has the following conditions: Available = True Progressing = False Failing = False 2. The clusteroperator's operator version is set to "0.0.1", when it should actually be set to "0.0.1-snapshot" so the CVO can replace this value. How reproducible: Always Steps to Reproduce: Create an Openshift cluster with the installer.
The content in "Status->Conditions" in the clusteroperator won't update during the cvo update progress. Some cluster operators changed and some didn't. didn't change clusteroperator list: operator-lifecycle-manager openshift-cloud-credential-operator monitoring marketplace-operator machine-api ingress image-registry dns cluster-storage-operator
For example, the OLM version is updated after the OTA. But the "conditions" timestamps are not changed. Before the upgarde: [jzhang@dhcp-140-18 upgrade-12]$ oc get clusteroperator operator-lifecycle-manager -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: 2019-03-13T03:59:53Z generation: 1 name: operator-lifecycle-manager resourceVersion: "7470" selfLink: /apis/config.openshift.io/v1/clusteroperators/operator-lifecycle-manager uid: 74e476cc-4544-11e9-b378-062e67fbace6 spec: {} status: conditions: - lastTransitionTime: 2019-03-13T03:59:53Z message: Done deploying 0.8.1. status: "False" type: Progressing - lastTransitionTime: 2019-03-13T03:59:53Z message: Done deploying 0.8.1. status: "False" type: Failing - lastTransitionTime: 2019-03-13T03:59:53Z message: Done deploying 0.8.1. status: "True" type: Available extension: null relatedObjects: null versions: - name: operator version: 0.8.1-416a6f1 After the upgarde: [jzhang@dhcp-140-18 upgrade-12]$ oc get clusteroperator operator-lifecycle-manager -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: 2019-03-13T03:59:53Z generation: 1 name: operator-lifecycle-manager resourceVersion: "275609" selfLink: /apis/config.openshift.io/v1/clusteroperators/operator-lifecycle-manager uid: 74e476cc-4544-11e9-b378-062e67fbace6 spec: {} status: conditions: - lastTransitionTime: 2019-03-13T03:59:53Z message: Done deploying 0.8.1. status: "False" type: Progressing - lastTransitionTime: 2019-03-13T03:59:53Z message: Done deploying 0.8.1. status: "False" type: Failing - lastTransitionTime: 2019-03-13T03:59:53Z message: Done deploying 0.8.1. status: "True" type: Available extension: null relatedObjects: null versions: - name: operator version: 0.8.1-ab6342f
one more PR : https://github.com/operator-framework/operator-marketplace/pull/134 for this bug will repair the probalistic measurement to "count of successful syncs ", and now it report the "payload version " as the operator version. will test again after this PR is merged in the nightly build.
PR https://github.com/operator-framework/operator-marketplace/pull/134 has been merged and is ready for review.
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:0758