Job:
periodic-ci-openshift-release-main-ci-4.22-e2e-aws-upgrade-ovn-single-node (all) - 3 runs, 0% failed, 67% of runs match
#2093280090036113408junit8 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.
#2093127264693653504junit19 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-multiarch-main-nightly-4.23-ocp-e2e-ovn-powervc-multi-p-p (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093247687439683584junit12 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-installer-release-4.20-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093070197253476352junit18 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-okd-scos-4.13-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093111356835237888junit19 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
periodic-ci-openshift-release-main-okd-scos-4.14-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093111359356014592junit19 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
periodic-ci-openshift-release-main-ci-4.15-upgrade-from-stable-4.14-e2e-gcp-ovn-rt-upgrade (all) - 2 runs, 0% failed, 50% of runs match
#2093125685383008256junit20 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.18-upgrade-from-stable-4.17-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093111063410118656junit20 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.19-upgrade-from-stable-4.18-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093112838359879680junit20 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-okd-scos-4.14-e2e-aws-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093112387337981952junit20 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
periodic-ci-openshift-release-main-nightly-4.17-upgrade-from-stable-4.16-e2e-aws-upgrade-ovn-single-node-network-flow-matrix (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093111744351178752junit20 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.17-upgrade-from-stable-4.16-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 0% failed, 100% of runs match
#2093112105573027840junit21 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.15-upgrade-from-stable-4.14-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093112103060639744junit21 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:

Found in 0.08% of runs (0.33% of failures) across 16941 total runs and 5832 jobs (23.11% failed) in 747ms - clear search | chart view - source code located on github