Job:
pull-ci-openshift-installer-release-4.14-e2e-gcp-ovn-upi (all) - 3 runs, 100% failed, 67% of failures match = 67% impact
#2114972841840480256junit7 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
#2114770028774559744junit17 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
rehearse-84347-periodic-ci-openshift-multiarch-main-nightly-4.19-ocp-e2e-ovn-agent-remote-s2s-libvirt-multi-p-p (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2114986118159011840junit7 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run.  These did not match any known exceptions, so they cause this test-case to fail:
pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-hypershift-conformance (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2114950015771217920junit10 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
periodic-ci-openshift-hypershift-release-5.1-periodics-e2e-aws-ovn-conformance-techpreview (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2114922304717721600junit12 hours ago
# [Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during (upgrade=false) e2e test run.  These did not match any known exceptions, so they cause this test-case to fail:

Found in 0.01% of runs (0.09% of failures) across 35450 total runs and 9538 jobs (14.89% failed) in 1.475s - clear search | chart view - source code located on github