Job:
openshift-ovn-kubernetes-3409-ci-4.21-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090378723386724352junit2 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-ocp-e2e-ovn-powervc-multi-p-p (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090348442764185600junit5 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-release-main-nightly-4.21-upgrade-from-stable-4.20-e2e-aws-upgrade-ovn-single-node (all) - 3 runs, 33% failed, 300% of failures match = 100% impact
#2090334784118067200junit5 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.
#2090239780108374016junit11 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.
#2090106342126653440junit20 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.
aggregated-gcp-ovn-rt-upgrade-5.1-major-release-openshift-release-analysis-aggregator (all) - 4 runs, 25% failed, 100% of failures match = 25% impact
#2090126894895730688junit18 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
#2090126894895730688junit18 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
periodic-ci-openshift-release-main-ci-5.0-upgrade-from-stable-4.22-e2e-azure-ovn-upgrade (all) - 40 runs, 45% failed, 6% of failures match = 3% impact
#2090116742700339200junit19 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:
pull-ci-openshift-installer-release-4.21-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090038872321822720junit20 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:
periodic-ci-openshift-release-main-nightly-4.21-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090034895337295872junit20 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:
periodic-ci-openshift-release-main-nightly-4.19-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090038369470910464junit22 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-openshift-release-main-ci-4.18-upgrade-from-stable-4.17-e2e-metal-ovn-single-node-rt-upgrade-test (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090039368151470080junit22 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
1 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-openshift-release-main-nightly-4.20-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090034591707435008junit22 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-openshift-release-main-nightly-4.17-upgrade-from-stable-4.16-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090039921686351872junit23 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.
periodic-ci-openshift-release-main-nightly-4.21-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090037638332420096junit23 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-release-main-nightly-4.21-upgrade-from-stable-4.20-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2090037870420037632junit24 hours ago
# [Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
1 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.04% of runs (0.20% of failures) across 37047 total runs and 8993 jobs (20.36% failed) in 7.739s - clear search | chart view - source code located on github