As much as 50% (possibly a bit lower) of jobs that upgrade GCP in PRs are failing because of the following alert firing during the run: disruption_tests: [sig-arch] Check if alerts are firing during or after upgrade success expand_less 1h11m50s Apr 12 16:28:39.842: Unexpected alerts fired or pending during the upgrade: alert AggregatedAPIDown fired for 136 seconds with labels: {name="v1.packages.operators.coreos.com", namespace="default", severity="warning"} https://search.ci.openshift.org/?search=AggregatedAPIDown.*packages&maxAge=120h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job It looks like this started happening in the last 48h (so sometime after Friday 4/9 and before Sunday 4/11). Marking urgent because most repos using GCP upgrade jobs are failing. Appears to be impacting AWS and vSphere jobs as well.
*** Bug 1949115 has been marked as a duplicate of this bug. ***
I didn't find the AggregatedAPIDown alert of packageserver for the latest 12 hours. Verify it.
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