Description of problem: Should use the production base image for the community CatalogSource pods. [root@preserve-olm-env data]# oc exec community-operators-5cl5r -- cat /etc/redhat-release cat: can't open '/etc/redhat-release': No such file or directory [root@preserve-olm-env data]# oc exec certified-operators-68dp7 -- cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.8 (Maipo) Version-Release number of selected component (if applicable): Cluster version is 4.6.0-0.nightly-2020-08-04-035157 How reproducible: Always Steps to Reproduce: 1. Install OCP 4.6. 2. Check the CatalogSource pod if use the production image. Actual results: Community operator doesn't use the production image. [root@preserve-olm-env data]# oc exec certified-operators-68dp7 -- cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.8 (Maipo) [root@preserve-olm-env data]# oc exec community-operators-5cl5r -- cat /etc/redhat-release cat: can't open '/etc/redhat-release': No such file or directory Expected results: I know these operators provided by this community image from the Community. But, it will be release as OCP production too. We should use the production image for it. Additional info:
Submitted Github issue - https://github.com/operator-framework/community-operators/issues/2388
Hi Luke, In before verrsions, for exmaple, 4.5, the community pods are based on RHEL, see: Cluster version is 4.5.0-0.nightly-2020-10-09-232128 [root@preserve-olm-env data]# oc get pods NAME READY STATUS RESTARTS AGE certified-operators-5fc4f665b6-s5hlq 1/1 Running 0 45m community-operators-7854fd85c7-tfkpw 1/1 Running 0 45m marketplace-operator-75b95c488-x7xvz 1/1 Running 0 45m redhat-marketplace-79755c8f99-wznbz 1/1 Running 0 45m redhat-operators-6fdbf8cfd-m6ckk 1/1 Running 0 45m [root@preserve-olm-env data]# oc rsh community-operators-7854fd85c7-tfkpw sh-4.2$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.9 (Maipo) sh-4.2$ exit I know there are some difference for the base image in 4.6, but, we still need to ship the image(registry.redhat.io/redhat/community-operator-index) to the customer, isn't it? If yes, we should make sure it based on RHEL. And, we use this registry.redhat.io/redhat/community-operator-index:latest image as the default Community Operator CatalogSource image. And, now, it based on RHEL, LGTM, verify it. [root@preserve-olm-env data]# oc get catalogsource community-operators -o yaml apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: creationTimestamp: "2020-10-09T02:57:56Z" ... spec: displayName: Community Operators icon: base64data: "" mediatype: "" image: registry.redhat.io/redhat/community-operator-index:latest priority: -400 publisher: Red Hat sourceType: grpc updateStrategy: registryPoll: interval: 10m0s ... [root@preserve-olm-env data]# oc rsh community-operators-9pl22 sh-4.2$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.8 (Maipo) sh-4.2$ exit exit
Cluster version is 4.6.0-0.nightly-2020-10-08-210814
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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196