Bug 2034409
| Summary: | Default CatalogSources should be pointing to 4.10 index images | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anik <anbhatta> |
| Component: | OLM | Assignee: | Kevin Rizza <krizza> |
| OLM sub component: | OperatorHub | QA Contact: | Jian Zhang <jiazha> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | jhadvig, nhale, xzha |
| Version: | 4.10 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.10.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: | 2022-03-10 16:35:34 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: | |||
| Bug Depends On: | 2035409 | ||
| Bug Blocks: | |||
|
Description
Anik
2021-12-20 20:27:52 UTC
I don't think we want to ship 4.10 without the initial 4.10 catalogs. Moving to blocker+. Looks like e2e-aws-console-olm is permafailing due to a hardcoded dependency on a member of the redhat-operators catalog that is not currently present in the 4.10 version of the index.
This will continue to fail until the test is updated to either:
- reference an operator that's present in the index
- not depend on the default indexes at all (preferred)
I've opened a BZ against console requesting the test be fixed: https://bugzilla.redhat.com/show_bug.cgi?id=2035409
If we run short on time before the release we can override the test and merge the image tag bump manually, with the caveat that we need to disable the test for greater downstream OLM until it's fixed.
Nick could you please recommend an operator selector that we could use instead? The failing suite is for creating a nemaspace from operator install page. So I think it should be pretty easy to replace the selector for one that is present in the 4.10. Thanks Looks good to me, verify it, details as follows,
[cloud-user@preserve-olm-env jian]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.10.0-0.nightly-2022-01-06-183041 True False 50m Cluster version is 4.10.0-0.nightly-2022-01-06-183041
[cloud-user@preserve-olm-env jian]$ oc get catalogsource
NAME DISPLAY TYPE PUBLISHER AGE
certified-operators Certified Operators grpc Red Hat 68m
community-operators Community Operators grpc Red Hat 68m
redhat-marketplace Red Hat Marketplace grpc Red Hat 68m
redhat-operators Red Hat Operators grpc Red Hat 68m
[cloud-user@preserve-olm-env jian]$ oc get catalogsource redhat-operators -o=jsonpath='{.spec.image}'
registry.redhat.io/redhat/redhat-operator-index:v4.10
[cloud-user@preserve-olm-env jian]$ oc get catalogsource community-operators -o=jsonpath='{.spec.image}'
registry.redhat.io/redhat/community-operator-index:v4.10
[cloud-user@preserve-olm-env jian]$ oc get catalogsource certified-operators -o=jsonpath='{.spec.image}'
registry.redhat.io/redhat/certified-operator-index:v4.10
[cloud-user@preserve-olm-env jian]$ oc get catalogsource redhat-marketplace -o=jsonpath='{.spec.image}'
registry.redhat.io/redhat/redhat-marketplace-index:v4.10
*** Bug 2018031 has been marked as a duplicate of this bug. *** The question of selector was answered: https://github.com/openshift/console/pull/10772 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.10.3 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-2022:0056 |