Bug 2011985 - SRO bundle references non-existent image
Summary: SRO bundle references non-existent image
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Special Resource Operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.0
Assignee: Brett Thurber
QA Contact: liqcui
URL:
Whiteboard:
Depends On: 2011977
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-07 20:45 UTC by OpenShift BugZilla Robot
Modified: 2021-10-18 17:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:52:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift special-resource-operator pull 53 0 None open [release-4.9] Bug 2011985: Use origin image in bundle 2021-10-07 20:45:22 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:52:42 UTC

Description OpenShift BugZilla Robot 2021-10-07 20:45:10 UTC 
+++ This bug was initially created as a clone of Bug #2011977 +++

Description of problem:
Currently we are unable to run the operator bundle in the openshift/special-resource-operator repository, because it uses a nonexistent image quay.io/openshift/special-resource-rhel8-operator:4.9. 

To be consistent with other optional operators we should be using the origin image quay.io/openshift/origin-special-resource-rhel8-operator:4.9.
Comment 3 liqcui 2021-10-12 01:55:59 UTC 
Verified Result:
$ operator-sdk run bundle quay.io/openshift-psap-qe/special-resource-operator-bundle:4.9.0
INFO[0007] Successfully created registry pod: uay-io-openshift-psap-qe-special-resource-operator-bundle-4-9-0 
INFO[0007] Created CatalogSource: openshift-special-resource-operator-catalog 
INFO[0007] OperatorGroup "operator-sdk-og" created      
INFO[0007] Created Subscription: openshift-special-resource-operator-v4-9-0-sub 
INFO[0013] Approved InstallPlan install-4pccw for the Subscription: openshift-special-resource-operator-v4-9-0-sub 
INFO[0013] Waiting for ClusterServiceVersion "default/openshift-special-resource-operator.v4.9.0" to reach 'Succeeded' phase 
INFO[0013]   Waiting for ClusterServiceVersion "default/openshift-special-resource-operator.v4.9.0" to appear 
INFO[0029]   Found ClusterServiceVersion "default/openshift-special-resource-operator.v4.9.0" phase: Pending 
INFO[0032]   Found ClusterServiceVersion "default/openshift-special-resource-operator.v4.9.0" phase: InstallReady 
INFO[0033]   Found ClusterServiceVersion "default/openshift-special-resource-operator.v4.9.0" phase: Installing 
INFO[0042]   Found ClusterServiceVersion "default/openshift-special-resource-operator.v4.9.0" phase: Succeeded 
INFO[0042] OLM has successfully installed "openshift-special-resource-operator.v4.9.0" 
[mirroradmin@ec2-18-217-45-133 special-resource-operator]$ oc get pods -n openshift-special-resource-operator
No resources found in openshift-special-resource-operator namespace.
[mirroradmin@ec2-18-217-45-133 special-resource-operator]$ oc get pods -A |grep special
default                                            special-resource-controller-manager-78c9564f6c-t2vvm                  2/2     Running     0             111s
default                                            uay-io-openshift-psap-qe-special-resource-operator-bundle-4-9-0       1/1     Running     0             2m20s
[mirroradmin@ec2-18-217-45-133 special-resource-operator]$ oc describe pod special-resource-controller-manager-78c9564f6c-t2vvm |grep -i image
    Image:         registry.redhat.io/openshift4/ose-kube-rbac-proxy
    Image ID:      registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:00e42b2a0f0dad10c8e87e33f0d0854fe3e4d4c05532dcb3ad695956f909000c
    Image:         quay.io/openshift/origin-special-resource-rhel8-operator:4.9
    Image ID:      quay.io/openshift/origin-special-resource-rhel8-operator@sha256:4133d75c354a0a34c46fee246be4c07b7290d4a6016fe93b0c6264f9a2af97b0
  Normal  Pulling         2m3s  kubelet            Pulling image "registry.redhat.io/openshift4/ose-kube-rbac-proxy"
  Normal  Pulled          119s  kubelet            Successfully pulled image "registry.redhat.io/openshift4/ose-kube-rbac-proxy" in 3.25048338s
  Normal  Pulling         119s  kubelet            Pulling image "quay.io/openshift/origin-special-resource-rhel8-operator:4.9"
  Normal  Pulled          116s  kubelet            Successfully pulled image "quay.io/openshift/origin-special-resource-rhel8-operator:4.9" in 3.495178114s
Comment 5 errata-xmlrpc 2021-10-18 17:52:32 UTC 
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.9.0 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-2021:3759
Note You need to log in before you can comment on or make changes to this bug.