| periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-arbiter-upgrade-day-2-workers (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2070711058707779584 | junit | 7 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-nightly-4.16-aws-ovn-network-flow-matrix-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2070643474205511680 | junit | 12 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.23-e2e-metal-ovn-two-node-fencing-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2070586233616076800 | junit | 13 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-4.14-e2e-aws-ovn-upgrade (all) - 7 runs, 57% failed, 25% of failures match = 14% impact | |||
| #2070626435675983872 | junit | 14 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 1 unexpected clusteroperator state transitions during e2e test run | |||
| periodic-ci-openshift-release-main-okd-scos-4.21-e2e-aws-ovn-upgrade (all) - 6 runs, 67% failed, 25% of failures match = 17% impact | |||
| #2070453892738453504 | junit | 22 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.02% of runs (0.09% of failures) across 23295 total runs and 6384 jobs (23.60% failed) in 4.132s - clear search | chart view - source code located on github