Job:
periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-etcd-scaling (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2117333235066212352junit2 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:
rehearse-88033-periodic-ci-openshift-hypershift-release-5.1-periodics-e2e-v2-azure-self-managed-backuprestore (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2117220760027140096junit8 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-ovn-kubernetes-main-e2e-aws-ovn-hypershift (all) - 9 runs, 44% failed, 25% of failures match = 11% impact
#2117081114269978624junit21 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:
periodic-ci-openshift-multiarch-main-nightly-4.21-ocp-e2e-upgrade-gcp-ovn-multi-a-a (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2117014631145803776junit23 hours ago
# [Monitor:legacy-cvo-invariants][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:

Found in 0.01% of runs (0.09% of failures) across 31903 total runs and 8835 jobs (14.70% failed) in 895ms - clear search | chart view - source code located on github