(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:

[sig-arch] events should not repeat pathologically

Extreme regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 99.03% to 0.00%.

Sample (being evaluated) Release: 4.20
Start Time: 2025-08-08T00:00:00Z
End Time: 2025-08-15T12:00:00Z
Success Rate: 0.00%
Successes: 0
Failures: 13
Flakes: 0
Base (historical) Release: 4.19
Start Time: 2025-05-18T00:00:00Z
End Time: 2025-06-17T23:59:59Z
Success Rate: 99.03%
Successes: 102
Failures: 1
Flakes: 0

View the test details report for additional context.

Every failure is:

sig-arch] events should not repeat pathologically expand_less 	0s
{  1 events happened too frequently

event happened 259 times, something is wrong: namespace/open-cluster-management-agent-addon node/ip-10-0-77-69.us-west-2.compute.internal pod/cluster-proxy-proxy-agent-645b4c874c-n7jsg hmsg/d5bf9afefc - reason/Failed Error: ImagePullBackOff (07:57:22Z) result=reject }

This test fails if we see over 20 identical events emitted, and is intended to prevent excessive load on the apiserver.

Component readiness regression and thus release blocker.

Filed by: dgoodwin@redhat.com