Job:
periodic-ci-openshift-multiarch-main-nightly-4.19-ocp-e2e-ovn-agent-remote-libvirt-multi-z-z (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2094198639378305024junit52 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-multiarch-main-nightly-5.0-ocp-e2e-ovn-powervs-capi-multi-p-p (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#2094168432411938816junit59 minutes 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-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
#2094138253102813184junit2 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.19-e2e-vsphere-ovn-etcd-scaling (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2094027428308455424junit9 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.23-ocp-e2e-ovn-powervc-multi-p-p (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093972229837557760junit15 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-upgrade-from-stable-4.20-e2e-metal-ovn-two-node-arbiter-upgrade-day-2-workers (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#2093851751613468672junit22 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.17-upgrade-from-stable-4.16-e2e-aws-upgrade-ovn-single-node-network-flow-matrix (all) - 2 runs, 50% failed, 100% of failures match = 50% impact
#2093836254931062784junit24 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.06% of runs (0.31% of failures) across 11978 total runs and 3981 jobs (19.13% failed) in 478ms - clear search | chart view - source code located on github