| 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 | |||
| #2066657177933713408 | junit | 20 minutes ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
| pull-ci-openshift-ovn-kubernetes-main-e2e-azure-ovn-upgrade (all) - 16 runs, 56% failed, 11% of failures match = 6% impact | |||
| #2066553354506473472 | junit | About an hour 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, 0% failed, 100% of runs match | |||
| #2066593909668057088 | junit | 3 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. | |||
| #2066510585360551936 | junit | 9 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. | |||
| #2066367530410184704 | junit | 18 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-5.0-e2e-metal-ovn-two-node-fencing-upgrade (all) - 2 runs, 50% failed, 100% of failures match = 50% impact | |||
| #2066448954442125312 | 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-multiarch-main-nightly-4.22-ocp-e2e-ovn-rhcos10-techpreview-multi-z-z (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2066460918396489728 | junit | 13 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-multiarch-main-nightly-4.14-upgrade-from-nightly-4.13-ocp-ovn-remote-libvirt-s390x (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2066437348240920576 | junit | 15 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run | |||
| periodic-ci-openshift-multiarch-main-nightly-4.21-upgrade-from-nightly-4.20-ocp-ovn-remote-libvirt-multi-z-z (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2066385403291635712 | junit | 17 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.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 | |||
| #2066294773219594240 | 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.03% of runs (0.16% of failures) across 31919 total runs and 7542 jobs (19.83% failed) in 374ms - clear search | chart view - source code located on github