Job:
periodic-ci-openshift-release-main-ci-4.12-upgrade-from-stable-4.11-e2e-azure-sdn-upgrade (all) - 7 runs, 71% failed, 60% of failures match = 43% impact
#2042901292438786048junit42 minutes ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
#2042758830076465152junit10 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
1 unexpected clusteroperator state transitions during e2e test run
#2042567745328910336junit22 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-ci-4.19-e2e-azure-runc-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042807251156078592junit5 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.12-upgrade-from-stable-4.11-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042820085613072384junit6 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
pull-ci-openshift-coredns-release-4.20-e2e-gcp-serial (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042758257889513472junit8 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.17-upgrade-from-nightly-4.16-ocp-ovn-remote-s2s-libvirt-multi-p-p (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042694393445486592junit15 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-cluster-storage-operator-release-4.23-periodics-periodic-e2e-vsphere-ovn-upgrade-check-dev-symlinks (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042644928995004416junit17 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-shiftstack-ci-release-4.14-e2e-openstack-ovn-parallel (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042666069771948032junit17 hours ago
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available
2 unexpected clusteroperator state transitions during e2e test run
aggregator-periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn-conformance (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042647370906210304junit18 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
pull-ci-openshift-api-master-e2e-aws-ovn-hypershift-conformance (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2042632252923318272junit18 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-5.0-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042595726394920960junit19 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-cluster-image-registry-operator-main-e2e-hypershift-conformance (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042605176740646912junit19 hours ago
# [Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available
6 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-ci-5.0-upgrade-from-stable-4.22-e2e-metal-ovn-single-node-rt-upgrade-test (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042595619024932864junit19 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.16-periodics-e2e-aws-ovn-conformance (all) - 3 runs, 67% failed, 50% of failures match = 33% impact
#2042608237248778240junit21 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-hypershift-release-4.20-periodics-mce-e2e-aws-ovn-conformance (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2042567189566853120junit21 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:

Found in 0.08% of runs (0.35% of failures) across 18996 total runs and 6429 jobs (23.85% failed) in 313ms - clear search | chart view - source code located on github