| periodic-ci-openshift-cluster-storage-operator-release-4.21-periodics-periodic-e2e-baremetal-ipi-ovn-upgrade-check-dev-symlinks (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069966338306084864 | junit | 5 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, 0% failed, 100% of runs match | |||
| #2069975664613658624 | 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. | |||
| #2069891479463006208 | junit | 11 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-e2e-azure-ovn-runc-techpreview (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069932364783423488 | junit | 6 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: | |||
| openshift-origin-31322-ci-4.20-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 0% failed, 100% of runs match | |||
| #2069965463248441344 | junit | 7 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.23-e2e-metal-ovn-two-node-fencing-upgrade (all) - 2 runs, 50% failed, 100% of failures match = 50% impact | |||
| #2069861395905646592 | junit | 12 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. | |||
| pull-ci-openshift-installer-main-e2e-openstack-proxy (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069768809882849280 | junit | 15 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: | |||
| aggregator-periodic-ci-openshift-release-main-ci-5.0-e2e-azure-ovn-upgrade-rhcos9-techpreview (all) - 2 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069806108158988288 | junit | 16 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 | |||
| #2069806108158988288 | junit | 16 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 | |||
| #2069806100554715136 | junit | 16 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 | |||
| #2069806100554715136 | junit | 16 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 | |||
| periodic-ci-openshift-release-main-nightly-4.20-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069739625357774848 | junit | 17 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: | |||
| pull-ci-openshift-cluster-version-operator-main-e2e-agnostic-ovn (all) - 5 runs, 80% failed, 25% of failures match = 20% impact | |||
| #2069765954480377856 | junit | 17 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-release-main-nightly-4.21-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069739899648479232 | junit | 17 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: | |||
| periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069742918087741440 | junit | 19 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-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069744948525142016 | 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.19-e2e-aws-ovn-etcd-scaling (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069743898468552704 | 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.22-upgrade-from-stable-4.21-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069743443105550336 | junit | 20 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.19-e2e-gcp-ovn-upi (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069743422159196160 | junit | 21 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.17-upgrade-from-stable-4.16-e2e-metal-ovn-single-node-rt-upgrade-test (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069739363301855232 | 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-okd-scos-4.13-e2e-aws-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069743665034563584 | junit | 21 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.21-e2e-aws-ovn-upgrade (all) - 5 runs, 80% failed, 25% of failures match = 20% impact | |||
| #2069729572001157120 | junit | 21 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: | |||
| 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 | |||
| #2069744143357186048 | junit | 22 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.15-upgrade-from-stable-4.14-from-stable-4.13-e2e-aws-sdn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069739358268690432 | junit | 22 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.13-upgrade-from-stable-4.12-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069743216965455872 | junit | 22 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-nightly-4.14-upgrade-from-stable-4.13-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2069738587133317120 | junit | 22 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 1 unexpected clusteroperator state transitions during e2e test run | |||
Found in 0.07% of runs (0.38% of failures) across 34648 total runs and 8648 jobs (18.36% failed) in 9.721s - clear search | chart view - source code located on github