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

[sig-cli] Kubectl logs all pod logs the Deployment has 2 replicas and each pod has 2 containers should get logs from each pod and each container in Deployment [Suite:openshift/conformance/parallel] [Suite:k8s]

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

Sample (being evaluated) Release: 4.20
Start Time: 2025-08-28T00:00:00Z
End Time: 2025-09-04T16:00:00Z
Success Rate: 93.75%
Successes: 60
Failures: 4
Flakes: 0
Base (historical) Release: 4.19
Start Time: 2025-05-18T00:00:00Z
End Time: 2025-06-17T23:59:59Z
Success Rate: 100.00%
Successes: 289
Failures: 0
Flakes: 3

View the test details report for additional context.

This is yet another k8s tests that lost the ability to retry, thus now occasionally shows up in component readiness because of the change in pass rate without the retry.

For 4.20 this late in the game, I'm going to restore the ability for this test to retry. We'll keep this bug open to address the underlying problem, and mark a release blocker for 4.21 to try again.

To runs runs where the test flakes in 4.21, use this link

The test always seems to fail with:

This is the same message we see when the test used to flake in prior releases.

Filed by: dgoodwin@redhat.com