Since 2022-01-19, CCM periodics are failing with: ``` [sig-instrumentation][Late] Alerts shouldn't report any unexpected alerts in firing or pending state [Suite:openshift/conformance/parallel] ``` see https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.10-e2e-openstack-ccm-install
This is most likely due to a change in the name of the test[1], which is making the TEST_SKIPS regex useless in our test definition[2]. [1]: https://github.com/openshift/origin/pull/26760 [2]: https://github.com/openshift/release/blob/a4579ba706f443d19295105d2c122e9b9399af6f/ci-operator/config/shiftstack/shiftstack-ci/shiftstack-shiftstack-ci-main__periodic-4.10.yaml#L133-L143
We should make it so that the `Alerts shouldn't report any unexpected alerts in firing or pending state` ignores the TechPreviewNoUpgrade alert.
The latest periodic[1] does not report the "unexpected alerts" failure. Moving to VERIFIED [1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.10-e2e-openstack-ccm-install/1486374781086339072
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