Job:
periodic-ci-openshift-release-main-ci-4.19-e2e-aws-upgrade-ovn-single-node (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2120796930035421184junit4 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.
pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.19-e2e-aws-ovn-etcd-scaling (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2120624543910334464junit15 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:
periodic-ci-shiftstack-ci-release-4.20-e2e-openstack-ovn-etcd-scaling (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2120562563216314368junit17 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:
aggregated-azure-ovn-upgrade-5.1-minor-release-openshift-release-analysis-aggregator (all) - 5 runs, 60% failed, 100% of failures match = 60% impact
#2120651131825688576junit18 hours ago
# openshift-tests.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should
#2120651131825688576junit18 hours ago
# openshift-tests-upgrade.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should
#2120647724004020224junit18 hours ago
# openshift-tests.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should
#2120647724004020224junit18 hours ago
# openshift-tests-upgrade.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should
#2120580698547949568junit18 hours ago
# openshift-tests.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should
#2120580698547949568junit18 hours ago
# openshift-tests-upgrade.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should
openshift-ovn-kubernetes-3627-ci-4.21-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 0% failed, 100% of runs match
#2120528309698695168junit22 hours ago
# [Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.
periodic-ci-openshift-multiarch-main-nightly-4.23-upgrade-from-stable-4.22-ocp-e2e-upgrade-aws-ovn-multi-a-a (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2120515188439388160junit22 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-release-main-ci-4.18-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 0% failed, 100% of runs match
#2120528536325328896junit23 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.
pull-ci-openshift-cluster-version-operator-release-4.14-e2e-hypershift-conformance (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2120522181669556224junit23 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run

Found in 0.03% of runs (0.12% of failures) across 39669 total runs and 9175 jobs (20.99% failed) in 514ms - clear search | chart view - source code located on github