Bug 1865815
Summary: | The community catalogSource pod should use the production base image | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> |
Component: | Release | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED ERRATA | QA Contact: | Jian Zhang <jiazha> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.6 | CC: | aos-bugs, jokerman, krizza, sd-ecosystem |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | 4.6.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: | 2020-10-27 16:23:12 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
Jian Zhang
2020-08-04 09:20:24 UTC
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 |