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

[Monitor:legacy-test-framework-invariants-pathological][sig-arch] events should not repeat pathologically

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

Sample (being evaluated) Release: 4.21
Start Time: 2026-01-07T00:00:00Z
End Time: 2026-01-14T16:00:00Z
Success Rate: 66.67%
Successes: 8
Failures: 4
Flakes: 0
Base (historical) Release: 4.20
Start Time: 2025-09-21T00:00:00Z
End Time: 2025-10-21T23:59:59Z
Success Rate: 100.00%
Successes: 31
Failures: 0
Flakes: 0

View the test details report for additional context.

Also showing in this report

Started just recently and has failed two of the last two in each of these reports.

Failure message:

 
[Monitor:legacy-test-framework-invariants-pathological][sig-arch] events should not repeat pathologically expand_less 	0s
{  1 events happened too frequently

event happened 94 times, something is wrong: namespace/openshift-cnv hmsg/7633531d0f migcontroller/migcontroller-kubevirt-hyperconverged - reason/UpdateResourceSuccess Successfully updated resource *v1.ClusterRole migrations.kubevirt.io:admin (06:13:43Z) result=reject }

Global CI search shows hits in 4.22 as well.

That is a lot of updates to a resource. Why would this suddenly start showing so late in 4.21?

Filed by: dgoodwin@redhat.com