Job:
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
#2053394203261538304junitAbout an hour 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.
#2053293327389822976junit8 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.
#2053127348206702592junit19 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.
rehearse-77967-periodic-ci-openshift-cluster-kube-apiserver-operator-main-periodics-e2e-aws-encryption-kms-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2053399600747778048junit3 hours ago
# [Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
12 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:
aggregated-aws-ovn-single-node-upgrade-5.0-micro-release-openshift-release-analysis-aggregator (all) - 4 runs, 50% failed, 100% of failures match = 50% impact
#2053339172504080384junit6 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
#2053339172504080384junit6 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
#2053258433271959552junit9 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
#2053258433271959552junit9 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.23-e2e-aws-ovn-single-node-4vcpu-32gb-compute-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2053270417954574336junit8 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.20-e2e-agent-ha-dualstack-conformance (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2053264235328180224junit10 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-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2053263617825968128junit11 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.19-ocp-e2e-serial-ovn-remote-s2s-libvirt-multi-p-p (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2053218640727117824junit13 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) - 6 runs, 67% failed, 50% of failures match = 33% impact
#2053204410795823104junit14 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
#2053093678741721088junit22 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.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
#2053188601755209728junit15 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
#2053123441896198144junit18 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-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
#2053112946657071104junit20 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
#2053112949169459200junit20 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.15% of runs (0.56% of failures) across 10971 total runs and 4129 jobs (26.18% failed) in 273ms - clear search | chart view - source code located on github