Description of problem: A new alert is being added to catalog-operator that fires when the installation of an operator generates warnings from the API server. The test https://github.com/openshift/origin/blob/d819d52f91b74dac893133110365c1651320035d/test/extended/operators/olm.go#L195 currently subscribes to amq-streams/stable, whose channel head uses the deprecated v1beta1 CustomResourceDefinition API and triggers the new alert. Version-Release number of selected component (if applicable): 4.8 How reproducible: Always Steps to Reproduce: 1. Observe ci job pull-ci-openshift-operator-framework-olm-master-e2e-gcp Actual results: amq-streams is installed Expected results: An operator that has migrated away from CRD v1beta1 is installed (current plan is to use cluster-logging).
verify it on 4.8. LGTM -- https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_operator-framework-olm/91/pull-ci-openshift-operator-framework-olm-master-e2e-gcp/1402695927046606848 --
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.8.2 bug fix and 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-2021:2438