| periodic-ci-openshift-multiarch-main-nightly-4.19-ocp-e2e-upgrade-gcp-ovn-multi-a-a (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2068495487769513984 | junit | 3 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-aws-upgrade-ovn-single-node-network-flow-matrix (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2068469163969482752 | junit | 5 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-ci-4.14-e2e-azure-ovn-upgrade (all) - 5 runs, 80% failed, 25% of failures match = 20% impact | |||
| #2068451432436076544 | junit | 6 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.21-upgrade-from-stable-4.20-e2e-aws-upgrade-ovn-single-node (all) - 3 runs, 33% failed, 300% of failures match = 100% impact | |||
| #2068436882273865728 | junit | 6 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. | |||
| #2068321066979168256 | 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. | |||
| #2068203026467786752 | junit | 22 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-hypershift-release-4.14-periodics-e2e-aws-ovn-conformance (all) - 4 runs, 100% failed, 50% of failures match = 50% impact | |||
| #2068471149024514048 | junit | 7 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run | |||
| #2068451432691929088 | junit | 8 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.21-upgrade-from-stable-4.20-e2e-aws-upgrade-ovn-single-node-network-flow-matrix (all) - 1 runs, 0% failed, 100% of runs match | |||
| #2068408764473544704 | junit | 8 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.23-e2e-vsphere-ovn-etcd-scaling (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2068296917544079360 | junit | 16 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: | |||
Found in 0.08% of runs (0.33% of failures) across 13240 total runs and 4354 jobs (22.76% failed) in 6.827s - clear search | chart view - source code located on github