Job:
periodic-ci-openshift-release-main-ci-4.14-e2e-aws-ovn-upgrade (all) - 3 runs, 67% failed, 50% of failures match = 33% impact
#2115827012806381568junitAbout an hour ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
periodic-ci-openshift-multiarch-main-nightly-4.22-upgrade-from-nightly-4.21-ocp-ovn-remote-libvirt-multi-z-z (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2115715682669694976junit8 hours ago
# [Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
0 unexpected clusteroperator state transitions during (upgrade=true) e2e test run, as desired.
periodic-ci-openshift-release-main-ci-5.0-upgrade-from-stable-4.22-e2e-azure-ovn-upgrade (all) - 29 runs, 45% failed, 8% of failures match = 3% impact
#2115690208925061120junit9 hours ago
# [Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during (upgrade=true) e2e test run.  These did not match any known exceptions, so they cause this test-case to fail:
periodic-ci-openshift-hypershift-release-5.1-periodics-e2e-aws-ovn-conformance (all) - 29 runs, 34% failed, 10% of failures match = 3% impact
#2115651439970750464junit15 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:
pull-ci-openshift-cluster-network-operator-main-e2e-aws-ovn-hypershift-conformance (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2115631000921837568junit16 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 35979 total runs and 9236 jobs (15.73% failed) in 486ms - clear search | chart view - source code located on github