| periodic-ci-openshift-release-main-ci-4.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade (all) - 4 runs, 100% failed, 25% of failures match = 25% impact | |||
| #2095229943075049472 | junit | 4 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.19-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2095112136840712192 | junit | 6 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-aws-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2095112386296942592 | junit | 10 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.22-upgrade-from-stable-4.21-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2095112168750977024 | junit | 11 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-nightly-4.16-upgrade-from-stable-4.15-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2095112866456670208 | junit | 11 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.13-upgrade-from-stable-4.12-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2095111856782839808 | junit | 12 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-ci-4.21-upgrade-from-stable-4.20-e2e-metal-ovn-single-node-rt-upgrade-test (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2094989798627348480 | junit | 14 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: | |||
| #2094989798627348480 | junit | 14 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-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade (all) - 4 runs, 75% failed, 33% of failures match = 25% impact | |||
| #2094936693525188608 | junit | 23 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
Found in 0.02% of runs (0.12% of failures) across 34530 total runs and 9689 jobs (20.01% failed) in 810ms - clear search | chart view - source code located on github