Job:
periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-aws-uwm (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1783639678637838336junit8 hours ago
# [sig-network-edge] Application behind service load balancer with PDB is not disrupted
Service was unreachable during disruption for at least 21s of 1h3m0s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-azure-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1783195739858407424junit37 hours ago
# [sig-network-edge] Application behind service load balancer with PDB is not disrupted
Service was unreachable during disruption for at least 1s of 1h16m25s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.8-upgrade-from-from-stable-4.7-from-stable-4.6-e2e-aws-upgrade (all) - 1 runs, 0% failed, 100% of runs match
#1783117876647956480junit42 hours ago
# [sig-network-edge] Application behind service load balancer with PDB is not disrupted
Service was unreachable during disruption for at least 25s of 2h13m2s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1782897767870369792junit2 days ago
# [sig-network-edge] Application behind service load balancer with PDB is not disrupted
Service was unreachable during disruption for at least 1m4s of 1h11m25s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-nightly-4.7-upgrade-from-stable-4.6-e2e-aws-upgrade (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
#1781781288349339648junit5 days ago
# [sig-network-edge] Application behind service load balancer with PDB is not disrupted
Service was unreachable during disruption for at least 16s of 1h1m0s (0%), this is currently sufficient to pass the test/job but not considered completely correct:

Found in 5.10% of runs (8.20% of failures) across 98 total runs and 42 jobs (62.24% failed) in 285ms - clear search | chart view - source code located on github