| rehearse-80478-periodic-ci-openshift-release-main-ci-4.22-e2e-azure-v7-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065468025892507648 | junit | 2 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-multiarch-main-nightly-4.15-upgrade-from-stable-4.14-ocp-e2e-upgrade-gcp-ovn-arm64 (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065456644996730880 | junit | 3 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.15-upgrade-from-stable-4.14-ocp-e2e-upgrade-azure-ovn-arm64 (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065449166410092544 | 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-ci-4.14-upgrade-from-stable-4.13-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065206200206626816 | 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-release-main-ci-4.15-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065207206789255168 | junit | 16 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.16-upgrade-from-stable-4.15-e2e-azure-sdn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065205948703576064 | junit | 18 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-okd-scos-4.13-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065205997240061952 | junit | 18 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-okd-scos-4.14-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065205999765032960 | junit | 19 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.18-upgrade-from-stable-4.17-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065205703462621184 | junit | 20 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 1 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.14-e2e-aws-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065207009640189952 | junit | 20 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.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 | |||
| #2065207631181516800 | junit | 20 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.15-upgrade-from-stable-4.14-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065206720157716480 | junit | 20 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 (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2065206722674298880 | junit | 21 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-upgrade-from-stable-4.13-e2e-azure-sdn-upgrade (all) - 5 runs, 40% failed, 50% of failures match = 20% impact | |||
| #2065129015491956736 | junit | 22 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run | |||
| aggregated-gcp-ovn-rt-upgrade-5.0-major-release-openshift-release-analysis-aggregator (all) - 9 runs, 100% failed, 33% of failures match = 33% impact | |||
| #2065221210685313024 | junit | 22 hours ago | |
# openshift-tests.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should | |||
| #2065221210685313024 | junit | 22 hours ago | |
# openshift-tests-upgrade.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should | |||
| #2065217989862494208 | junit | 23 hours ago | |
# openshift-tests.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should | |||
| #2065217989862494208 | junit | 23 hours ago | |
# openshift-tests-upgrade.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should | |||
| #2065138864523055104 | junit | 23 hours ago | |
# openshift-tests.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should | |||
| #2065138864523055104 | junit | 23 hours ago | |
# openshift-tests-upgrade.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should | |||
| 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 | |||
| #2065147166850027520 | junit | 23 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.21-upgrade-from-stable-4.20-e2e-aws-upgrade-ovn-single-node (all) - 2 runs, 100% failed, 50% of failures match = 50% impact | |||
| #2065152316213825536 | junit | 23 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. | |||
Found in 0.07% of runs (0.23% of failures) across 25819 total runs and 6608 jobs (31.86% failed) in 399ms - clear search | chart view - source code located on github