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

[sig-network-edge][Conformance][Area:Networking][Feature:Router][apigroup:route.openshift.io][apigroup:config.openshift.io] The HAProxy router should pass the http2 tests [apigroup:image.openshift.io][apigroup:operator.openshift.io] [Suite:openshift/conformance/parallel/minimal]

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

Sample (being evaluated) Release: 4.21
Start Time: 2025-10-08T00:00:00Z
End Time: 2025-10-15T08:00:00Z
Success Rate: 94.69%
Successes: 190
Failures: 11
Flakes: 6
Base (historical) Release: 4.20
Start Time: 2025-09-15T00:00:00Z
End Time: 2025-10-15T08:00:00Z
Success Rate: 100.00%
Successes: 920
Failures: 0
Flakes: 0

View the test details report for additional context.

This actually affects several tests and they always seem to fail when the ingress controller has gone Progressing in the middle of e2e testing. Sometimes it happens twice and the test fails it's retry, sometimes just once and it gets marked a flake. Neither was occurring in 4.20 so this appears to be a new problem.

From an affected job run, go to Debug Tools, Intervals, Files > select the second spyglass file, this is the post-upgrade conformance testing phase. You will see a somewhat random selection of network edge test failures overlapping with operator progressing.

Side note, keep an eye out if the operator should be Progressing vs Degraded here, this feels more like degraded to me.

Thus far, we're only seeing this on Azure.

Filed by: dgoodwin@redhat.com