Job:
periodic-ci-openshift-release-master-nightly-4.9-upgrade-from-stable-4.8-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1779920330412789760junit13 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m48s of 2h32m23s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.8-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1779827266033815552junit19 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 42s of 2h32m27s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1779247807014637568junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
disruption checking is disabled for prior releases because we lack a good baseline: Frontends were unreachable during disruption for at least 56m36s of 1h26m34s (65%):
periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-aws-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1779192693713276928junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 41s of 1h21m34s (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-aws-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1778979285017563136junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 1h4m34s (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
#1778911588149891072junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3m14s of 1h13m14s (4%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1778702286722174976junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Apr 12 10:36:34.370: Frontends were unreachable during disruption for at least 22m34s of 1h26m8s (26%):
periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-gcp-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1778618720210391040junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Apr 12 04:56:47.176: Frontends were unreachable during disruption for at least 59m32s of 1h21m48s (73%):
periodic-ci-openshift-release-master-ci-4.8-e2e-gcp-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1778262257533194240junit5 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 0s of 1h9m47s (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-azure-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1778122334071164928junit5 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h22m1s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-from-stable-4.7-e2e-aws-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1777966304645353472junit5 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 40s of 2h34m10s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.9-e2e-gcp-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1777901375787634688junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3m19s of 1h8m29s (5%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-azure-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1777768655845593088junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Apr  9 21:15:25.074: Frontends were unreachable during disruption for at least 24m38s of 1h48m23s (23%):
periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-azure-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1777772429909692416junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 1h12m40s (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
#1777682083712339968junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 40s of 2h15m28s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-aws-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1777633010091298816junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Apr  9 11:31:43.058: Frontends were unreachable during disruption for at least 19m30s of 1h19m25s (25%):

Found in 0.01% of runs (0.05% of failures) across 124572 total runs and 8090 jobs (23.98% failed) in 5.344s - clear search | chart view - source code located on github