Description of problem: A console e2e test depends on an operator package that isn't published to the default 4.10 redhat-operators catalog, causing it to fail in PRs attempting to bump the catalog image from 4.9 to 4.10; in-turn, blocking the release. Thoughts: Ideally, these tests shouldn't depend on specific optional content shipped in OpenShift catalogs. However, if we find ourselves short on time, we could be unblocked by depending on a different operator; one that's available in the 4.10 catalog. Alternatively, we could override or disable the test in the short-term, although that will leave us (OLM) open to regressing. See also: Hardcoded dependency: https://github.com/openshift/console/blob/f240986d7751abcf3292ed6522b3b78c5c87a5c5/frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/create-namespace.spec.ts#L26 PR blocked by `e2e-aws-console` (prow job that runs the console test for operator-marketplace): https://github.com/operator-framework/operator-marketplace/pull/456#issuecomment-1000565909 Example of a failed test: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/operator-framework_operator-marketplace/456/pull-ci-operator-framework-operator-marketplace-master-e2e-aws-console-olm/1467862771302404096 4.10 catalog: registry.redhat.io/redhat/redhat-operator-index:v4.10 4.9 catalog: registry.redhat.io/redhat/redhat-operator-index:v4.9
Weird that 'Advanced Cluster Management for Kubernetes' with the data-test 'advanced-cluster-management-redhat-operators-openshift-marketplace' attribute isn't published to the default 4.10 redhat-operators catalog. @David please check https://github.com/operator-framework/operator-marketplace/pull/456#issuecomment-1003996499
Reassigning to Dev Console as I am not familiar with this OLM test & operator usage.
> Weird that 'Advanced Cluster Management for Kubernetes' with the data-test 'advanced-cluster-management-redhat-operators-openshift-marketplace' attribute isn't published to the default 4.10 redhat-operators catalog. @jhadvig, there's no guarantee that the operator will be present in the catalog shipped with 4.11, or 4.12, or any future minor release of OpenShift. This is because we've switched the publishing strategy from publishing a single catalog to all minor releases to publishing a unique catalog for each minor release. I've also responded with a suggestion about how we could drop the marketplace dependency in short order: https://github.com/operator-framework/operator-marketplace/pull/456#issuecomment-1004180277 > Reassigning to Dev Console as I am not familiar with this OLM test & operator usage. @jhadvig @dtaylor isn't the component under test here part of the admin console? has that changed? If not, I don't think this bug should be listed under the dev console.
No this should stay under Management Console component. Assigning to Harish since he was working on this piece.
Cluster Version: 4.10.0-0.nightly-2022-01-07-181043 Verified that the catalog source is now changed to the operator that is available.
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