https://github.com/operator-framework/operator-lifecycle-manager/pull/979 cherry-pick is here, but we need 1717638 to be verified first.
I believe the 979 PR has been improperly attributed to this bug. The 4.1 fix for this bug never was made.
Current the latest payload is 4.1.0-0.nightly-2019-09-13-212451, which the fixed PR hasn't merged in. oc adm release info registry.svc.ci.openshift.org/ocp/release:4.1.0-0.nightly-2019-09-13-212451 --commits | grep operator-lifecycle-manager operator-lifecycle-manager https://github.com/operator-framework/operator-lifecycle-manager 616650ea46ec9c741d6ad9b306b556520f6975e1 Change status to MODIFIED.
LGTM, marking as VERIFIED. OLM Cluster Operators have the related resources defined as expected Cluster Version: 4.1.0-0.nightly-2019-09-18-141128 OLM version: 0.9.0 git commit: 51dcee9 Steps used to verify: oc get co operator-lifecycle-manager -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-09-18T15:27:21Z" generation: 1 name: operator-lifecycle-manager resourceVersion: "10369" selfLink: /apis/config.openshift.io/v1/clusteroperators/operator-lifecycle-manager uid: cf1de31b-da28-11e9-919f-02e1c3a93ea8 spec: {} status: conditions: - lastTransitionTime: "2019-09-18T15:27:22Z" status: "False" type: Degraded - lastTransitionTime: "2019-09-18T15:32:27Z" message: Deployed 0.9.0 status: "False" type: Progressing - lastTransitionTime: "2019-09-18T15:27:22Z" status: "True" type: Available - lastTransitionTime: "2019-09-18T15:27:22Z" status: "True" type: Upgradeable extension: null relatedObjects: - group: operators.coreos.com name: packageserver.v0.9.0 namespace: openshift-operator-lifecycle-manager resource: ClusterServiceVersion - group: "" name: openshift-operator-lifecycle-manager resource: namespaces versions: - name: operator version: 4.1.0-0.nightly-2019-09-18-141128 - name: operator-lifecycle-manager version: 0.9.0 oc get co operator-lifecycle-manager-catalog -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-09-18T15:27:21Z" generation: 1 name: operator-lifecycle-manager-catalog resourceVersion: "10371" selfLink: /apis/config.openshift.io/v1/clusteroperators/operator-lifecycle-manager-catalog uid: cf1a666f-da28-11e9-919f-02e1c3a93ea8 spec: {} status: conditions: - lastTransitionTime: "2019-09-18T15:27:21Z" status: "False" type: Degraded - lastTransitionTime: "2019-09-18T15:32:27Z" message: Deployed 0.9.0 status: "False" type: Progressing - lastTransitionTime: "2019-09-18T15:27:21Z" status: "True" type: Available - lastTransitionTime: "2019-09-18T15:27:21Z" status: "True" type: Upgradeable extension: null relatedObjects: - group: operators.coreos.com name: packageserver namespace: openshift-operator-lifecycle-manager resource: Subscription - group: operators.coreos.com name: install-thnj4 namespace: openshift-operator-lifecycle-manager resource: InstallPlan - group: "" name: openshift-operator-lifecycle-manager resource: namespaces versions: - name: operator version: 4.1.0-0.nightly-2019-09-18-141128 - name: operator-lifecycle-manager version: 0.9.0
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:2820