Job:
periodic-ci-openshift-multiarch-main-nightly-4.18-ocp-e2e-ovn-remote-libvirt-s390x (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2031792484018819072junit50 minutes 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
#2031808443823689728junit3 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.
#2031548088656596992junit20 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.
aggregator-periodic-ci-openshift-release-main-ci-4.22-e2e-azure-ovn-upgrade (all) - 2 runs, 50% failed, 100% of failures match = 50% impact
#2031783987973722112junit3 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
#2031783987973722112junit3 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-okd-scos-4.22-e2e-aws-ovn-upgrade (all) - 6 runs, 50% failed, 33% of failures match = 17% impact
#2031789539491581952junit4 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-ci-4.15-upgrade-from-stable-4.14-e2e-azure-sdn-upgrade (all) - 5 runs, 60% failed, 33% of failures match = 20% impact
#2031720756764741632junit8 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.18-e2e-gcp-ovn-upgrade (all) - 4 runs, 75% failed, 33% of failures match = 25% impact
#2031720967268470784junit9 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.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade (all) - 4 runs, 25% failed, 100% of failures match = 25% impact
#2031720967167807488junit9 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-kube-apiserver-operator-main-e2e-gcp-operator-serial-ote (all) - 7 runs, 57% failed, 25% of failures match = 14% impact
#2031691229174960128junit12 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:
rehearse-75996-periodic-ci-openshift-multiarch-main-nightly-4.19-ocp-e2e-compact-ovn-remote-libvirt-multi-z-z (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2031699703724249088junit12 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-5.0-e2e-metal-ovn-two-node-fencing-upgrade-techpreview (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2031659699945869312junit12 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-ci-4.21-e2e-aws-upgrade-ovn-single-node (all) - 3 runs, 67% failed, 50% of failures match = 33% impact
#2031547977922777088junit20 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-aws-ovn-single-node-4vcpu-32gb-compute-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2031499480548773888junit23 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-aws-upgrade-ovn-single-node-network-flow-matrix (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2031505655369568256junit23 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.04% of runs (0.19% of failures) across 33426 total runs and 7189 jobs (21.62% failed) in 383ms - clear search | chart view - source code located on github