Bug 1705135
Summary: | Operators installed to resolve a dependency can not be updated | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | David Zager <dzager> |
Component: | OLM | Assignee: | Evan Cordell <ecordell> |
OLM sub component: | OLM | QA Contact: | Jian Zhang <jiazha> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | scuppett |
Version: | 4.1.0 | ||
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:48:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Zager
2019-05-01 15:25:25 UTC
Verified that the dependent subscription seems to be stuck in upgradepending. This is fixed in this PR: https://github.com/operator-framework/operator-lifecycle-manager/pull/838 LGTM, verify it. Details as below: OLM version: io.openshift.build.commit.id=b2d1cd21368bc8cc10e4ca11a231f09077630c33 Cluster version is 4.1.0-0.nightly-2019-05-06-011159 The steps as the original description shows, Update that ConfigMap, as below: mac:~ jianzhang$ oc apply -f https://raw.githubusercontent.com/djzager/olm-playground/d3edd369ca7fd1e800c2dd096f57ebc67eeb6545/scenario2/configmap/scenario2-v2.configmap.yaml Warning: oc apply should be used on resource created by either oc create --save-config or oc apply configmap/scenario2 configured Check the image of example-operator-b, it's the docker.io/djzager/example-operator-b:v2, LGTM. mac:~ jianzhang$ oc get pods -n scenario2 NAME READY STATUS RESTARTS AGE example-operator-a-59c7fffd7f-m2zzq 2/2 Running 0 5m41s example-operator-b-d86647689-qdg6t 2/2 Running 0 57s mac:~ jianzhang$ oc get pods -n scenario2 example-operator-b-d86647689-qdg6t -o yaml|grep image image: docker.io/djzager/example-operator-b:v2 imagePullPolicy: IfNotPresent image: docker.io/djzager/example-operator-b:v2 imagePullPolicy: IfNotPresent imagePullSecrets: image: docker.io/djzager/example-operator-b:v2 imageID: docker.io/djzager/example-operator-b@sha256:7c6fe505434f2e70f368c41534f4c21297402756571815f52b4d5a4254d2e8fc image: docker.io/djzager/example-operator-b:v2 imageID: docker.io/djzager/example-operator-b@sha256:7c6fe505434f2e70f368c41534f4c21297402756571815f52b4d5a4254d2e8fc 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 |