| periodic-ci-openshift-multiarch-main-nightly-4.19-ocp-e2e-serial-ovn-remote-s2s-libvirt-multi-p-p (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2053218640727117824 | junit | 2 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-ci-4.12-upgrade-from-stable-4.11-e2e-azure-sdn-upgrade (all) - 7 runs, 86% failed, 50% of failures match = 43% impact | |||
| #2053204410795823104 | junit | 3 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run | |||
| #2053093678741721088 | junit | 11 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 1 unexpected clusteroperator state transitions during e2e test run | |||
| #2053035613292072960 | junit | 14 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, 100% failed, 100% of failures match = 100% impact | |||
| #2053188601755209728 | junit | 4 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.19-periodics-e2e-kubevirt-azure (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2053123441896198144 | junit | 7 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.21-upgrade-from-stable-4.20-e2e-aws-upgrade-ovn-single-node (all) - 2 runs, 50% failed, 200% of failures match = 100% impact | |||
| #2053127348206702592 | 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. | |||
| #2052985923011874816 | 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-multiarch-main-nightly-4.15-upgrade-from-stable-4.14-ocp-e2e-upgrade-azure-ovn-heterogeneous (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2053112946657071104 | junit | 8 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-multiarch-main-nightly-4.16-upgrade-from-stable-4.15-ocp-e2e-upgrade-gcp-ovn-arm64 (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2053112949169459200 | junit | 9 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-5.0-e2e-aws-upgrade-ovn-single-node (all) - 37 runs, 57% failed, 5% of failures match = 3% impact | |||
| #2052926048542134272 | junit | 21 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-hypershift-release-4.14-periodics-e2e-aws-ovn-conformance (all) - 3 runs, 33% failed, 100% of failures match = 33% impact | |||
| #2052958619581812736 | junit | 22 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run | |||
Found in 0.09% of runs (0.40% of failures) across 12810 total runs and 4805 jobs (23.40% failed) in 283ms - clear search | chart view - source code located on github