Red Hat Bugzilla – Bug 1619101
Should build the downstream image for the OLM
Last modified: 2018-10-11 03:25:45 EDT
Description of problem: At present, the OLM component uses the upstream image: quay.io/coreos/olm@sha256:44b445850b3e612c062424c3727bb85048ec8e71407b39985786d29aa20f5c79 quay.io/coreos/catalog@sha256:20886d49205aa8d8fd53f1c85fad6a501775226da25ef14f51258b7066e91064 Version-Release number of selected component (if applicable): OCP version: v3.11.0-0.17.0 olm version: 0.6.0-rhel How reproducible: always Steps to Reproduce: 1. Install the olm component in the OCP via the openshift-ansible. 2. Check their images. Actual results: [root@qe-jiazha-round3master-etcd-1 ~]# oc get pods NAME READY STATUS RESTARTS AGE alm-operator-798c765f5c-8h9t2 1/1 Running 0 3h catalog-operator-548958ff7f-d2lqn 1/1 Running 0 3h [root@qe-jiazha-round3master-etcd-1 ~]# oc get pods -o yaml | grep image image: quay.io/coreos/olm@sha256:44b445850b3e612c062424c3727bb85048ec8e71407b39985786d29aa20f5c79 imagePullPolicy: IfNotPresent imagePullSecrets: image: quay.io/coreos/olm@sha256:44b445850b3e612c062424c3727bb85048ec8e71407b39985786d29aa20f5c79 imageID: docker-pullable://quay.io/coreos/olm@sha256:44b445850b3e612c062424c3727bb85048ec8e71407b39985786d29aa20f5c79 image: quay.io/coreos/catalog@sha256:20886d49205aa8d8fd53f1c85fad6a501775226da25ef14f51258b7066e91064 imagePullPolicy: IfNotPresent imagePullSecrets: image: quay.io/coreos/catalog@sha256:20886d49205aa8d8fd53f1c85fad6a501775226da25ef14f51258b7066e91064 imageID: docker-pullable://quay.io/coreos/catalog@sha256:20886d49205aa8d8fd53f1c85fad6a501775226da25ef14f51258b7066e91064 Expected results: Should build and use the downstream images for them. Additional info: These images were hardcode in the ansible file: https://github.com/openshift/openshift-ansible/blob/master/roles/olm/files/13-catalog-operator.deployment.yaml#L30 https://github.com/openshift/openshift-ansible/blob/master/roles/olm/files/12-alm-operator.deployment.yaml#L27
If these values are hard coded in the openshift-ansible project then I am confused as to why there was a ticket opened against the OCP Release component. Would a better place for this issue not have been the Installer OCP component instead?
Tim, I don't think so. AFAIK, they have NOT the downstream images yet by now. We need to provide the downstream images firstly, don't we? Change the component to the "Release" first, correct me if I'm wrong. Added Evan who is the developer of the OLM in here.
We've requested a repo in distgit and will follow up as soon as we have it.
Evan & Tim, For the hardcode issue, I created bug 1620329 to trace it.
Evan, The downstream image is ready now? If yes, can you tell me the name of the downstream image? I could not find it in the latest OCP build(oc v3.11.0-0.24.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-2018:2652