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

TestCreateCluster

Extreme regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 96.91% to 76.27%.
Regression is triaged, and believed fixed as of 2025-09-19T19:15:42Z, but failures have been observed as recently as 2025-09-21T01:12:22Z.

Sample (being evaluated) Release: 4.20
Start Time: 2025-09-16T00:00:00Z
End Time: 2025-09-23T12:00:00Z
Success Rate: 76.27%
Successes: 45
Failures: 14
Flakes: 0
Base (historical) Release: 4.17
Start Time: 2024-09-01T00:00:00Z
End Time: 2024-10-01T00:00:00Z
Success Rate: 96.91%
Successes: 376
Failures: 12
Flakes: 0

View the test details report for additional context.

The report above is how I found the issue, but the specific test TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods appears to be a separate failure mode, mixed in with another now fixed issue you'll see in the report when the test went from fully red to green.

The two hits in the other job run are what found this issue. This is not technically enough to fail on their own, so I will not flag this release blocker, but this test looks to be failing enough that it WILL be an issue in the future at some point if not addressed.

Failure mode:

{Failed  === RUN   TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
    util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k2zfn/create-cluster-gg482 in 0s
    util.go:276: Successfully waited for kubeconfig secret to have data in 0s
    util.go:755: Container kube-apiserver in pod kube-apiserver-d8b97b6f5-5lzqx has a restartCount > 0 (1)
        --- FAIL: TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods (0.03s)
}

For all runs where this is failing see this list.

Filed by: dgoodwin@redhat.com