Component Readiness has found a potential regression in the following tests:

[sig-arch] events should not repeat pathologically for ns/openshift-cluster-csi-drivers

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

API LBs follow /readyz of kube-apiserver and stop sending requests before server shutdowns for external clients

Test has a 69.57% pass rate, but 95.00% is required.

[sig-network][Feature:Router][apigroup:route.openshift.io] The HAProxy router converges when multiple routers are writing conflicting status [Suite:openshift/conformance/parallel]

Significant regression detected.
Fishers Exact probability of a regression: 99.98%.
Test pass rate dropped from 99.51% to 94.00%.

[sig-node] node-lifecycle detects unexpected not ready node

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

[sig-node] node-lifecycle detects unreachable state on node

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

[sig-arch] events should not repeat pathologically

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

[sig-arch][Late] clients should not use APIs that are removed in upcoming releases [apigroup:apiserver.openshift.io] [Suite:openshift/conformance/parallel]

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

Useful Component Readiness Links:

We are proving the following two links for your convenience:

• Click here to access a snapshot of the component readiness page at the time this issue was generated.

• Click here to access the component readiness page with latest data. This is useful for developers to verify their fixes.

Recommendations:

This is an automatically generated Jira card against the component based on stats generated from component readiness dashboard. Here are some useful recommendations when dealing with this card:

• It is best to use this card as a placeholder for all the regressed tests for your component. A linked issue can be created for each regressed test. Please only close this issue when all known regressed tests are believed fixed.

• Please do not remove 'Release Blocker' label. The bot will automatically add it back if regressed tests continue showing for the component.