Job:
#1872471bug3 weeks ago[sig-network-edge] Cluster frontend ingress remain available ASSIGNED
Bug 1872471: [sig-network-edge] Cluster frontend ingress remain available
Status: ASSIGNED
test:
[sig-network-edge] Cluster frontend ingress remain available
#1843183bug3 weeks agoOverly broad test-case label: [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial] POST
<testcase name="Check if critical alerts are firing after upgrade success" classname="disruption_tests" time="3713.923365053">
<testcase name="Cluster frontend ingress remain available" classname="disruption_tests" time="3400.179978014">
<testcase name="Application behind service load balancer with PDB is not disrupted" classname="disruption_tests" time="3460.234515131">
#1878888bug3 weeks agoCluster frontend ingress remain available NEW
Bug 1878888: Cluster frontend ingress remain available
Status: NEW
test:
Cluster frontend ingress remain available
#1879961bug17 hours ago[sig-network-edge] Cluster frontend ingress remain available NEW
Bug 1879961: [sig-network-edge] Cluster frontend ingress remain available
Status: NEW
Component: Routing
Environment:[sig-network-edge] Cluster frontend ingress remain available Cluster frontend ingress remain available
---
test:
[sig-network-edge] Cluster frontend ingress remain available
#1871299bug3 weeks agoCluster frontend ingress remain available ASSIGNED
Bug 1871299: Cluster frontend ingress remain available
Status: ASSIGNED
test:
Cluster frontend ingress remain available
release-openshift-origin-installer-e2e-aws-ovn-upgrade-4.5-stable-to-4.6-ci - 42 runs, 100% failed, 86% of failures match
#1319871110136729600junit32 minutes ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 41s of 2h33m35s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319831353167974400junit4 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 12s of 1h45m30s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319779518201729024junit7 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 33s of 2h33m45s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319727551093936128junit10 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Oct 23 22:58:43.568: Frontends were unreachable during disruption for at least 1h22m16s of 2h35m17s (53%):
#1319643689374453760junit16 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3m27s of 2h32m57s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319601415332564992junit19 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 27s of 1h56m13s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319558648678060032junit22 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 39s of 1h57m11s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319517377167101952junit25 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 40s of 1h51m33s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319466287478345728junit27 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 2h33m19s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319412222862036992junit31 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 48s of 2h33m3s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319322106818727936junit38 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 13s of 1h45m40s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319361109781647360junit34 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 37s of 2h33m55s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319270756391063552junit40 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 12s of 2h33m55s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319217539938521088junit44 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 8s of 2h35m6s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319163683087060992junit47 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 7s of 2h33m44s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319124167739576320junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 21s of 1h48m24s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319072050630889472junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 20s of 2h33m9s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319020971201400832junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3m11s of 2h35m12s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318980701827108864junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3m20s of 1h50m37s (3%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318925662181920768junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 5m28s of 2h33m11s (4%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318874162063740928junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m5s of 2h33m5s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318801927978356736junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 6s of 1h59m36s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318758132410748928junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 45s of 2h4m54s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318718370194919424junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3s of 1h52m22s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318677858016563200junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m32s of 1h47m47s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318637596217184256junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m9s of 1h51m45s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318596325528309760junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 41s of 1h54m15s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318554819702558720junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 6s of 1h55m44s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318501817310515200junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3m42s of 2h33m3s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318404663900377088junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m13s of 1h56m4s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318351812910125056junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m54s of 2h34m23s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318446189737152512junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 2h34m2s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318297956163522560junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 35s of 2h33m57s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317441449658159104junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Oct 17 15:34:06.298: Frontends were unreachable during disruption for at least 1h24m50s of 2h33m53s (55%):
#1317402444870717440junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 57s of 1h48m15s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317341793578127360junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Oct 17 08:55:09.845: Frontends were unreachable during disruption for at least 1h51m47s of 2h33m3s (73%):
release-openshift-origin-installer-e2e-gcp-ovn-upgrade-4.4-stable-to-4.5-ci - 20 runs, 25% failed, 300% of failures match
#1319893253213917184junit50 minutes ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 31s of 49m24s (1%):
#1319802415993589760junit7 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 36s of 56m44s (1%):
#1319711697530785792junit13 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 6s of 50m5s (0%):
#1318440148769181696junit13 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 35s of 52m18s (1%):
#1319620788113903616junit19 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 12s of 55m42s (0%):
#1319529959202492416junit25 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 9s of 54m30s (0%):
#1319439125606043648junit31 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 7s of 50m46s (0%):
#1319166703568949248junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 16s of 48m22s (1%):
#1319075821532483584junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 25s of 48m38s (1%):
#1318984977991340032junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 19s of 53m19s (1%):
#1318894198744682496junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 13s of 49m32s (0%):
#1318803435549626368junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 17s of 54m56s (1%):
#1318621738455535616junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 40s of 57m31s (1%):
#1318349299196628992junit4 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 18s of 55m32s (1%):
#1317440946379427840junit6 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 17s of 48m24s (1%):
release-openshift-origin-installer-e2e-aws-upgrade-4.5-stable-to-4.6-ci - 57 runs, 19% failed, 245% of failures match
#1319880174312886272junitAbout an hour ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 49s of 1h9m40s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319847711742103552junit3 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 1h13m54s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319813987096858624junit6 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 56s of 1h13m44s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319747420942241792junit10 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 42s of 1h16m34s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319681243624771584junit15 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 1h4m47s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319581052376715264junit21 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 43s of 1h5m29s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319518383087030272junit25 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 42s of 1h9m33s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319487932272218112junit27 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 12s of 1h4m22s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319455728078950400junit29 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 47s of 1h8m25s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319388583705972736junit34 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 5s of 1h9m37s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319355309013078016junit36 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 1h8m22s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319224955073728512junit45 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 42s of 1h11m39s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319194134770094080junit47 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 8s of 1h5m37s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319158900393512960junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m2s of 1h12m48s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319028275992858624junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 1h16m22s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318995806857990144junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 24s of 1h7m43s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318867618425212928junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 8s of 1h9m49s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318773988855386112junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 7s of 1h5m35s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318705284822077440junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 8s of 1h10m11s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318576696328196096junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 27s of 1h9m5s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318451727564804096junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h4m13s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318421276104069120junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h8m29s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318389564330479616junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 1h15m52s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318359113142374400junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 18s of 1h12m16s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317475421658288128junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h11m2s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317444972793827328junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 1h8m7s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317384071818514432junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 11s of 1h4m41s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
release-openshift-origin-installer-e2e-gcp-upgrade-4.5-stable-to-4.6-ci - 21 runs, 19% failed, 425% of failures match
#1319854757547872256junit3 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m25s of 1h6m31s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319763909720150016junit9 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m44s of 1h5m17s (3%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319673184999444480junit15 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m45s of 1h8m23s (3%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319582308910501888junit21 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m3s of 1h1m18s (3%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319491460881453056junit27 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 47s of 1h0m50s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319400647983894528junit33 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m16s of 1h3m30s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319218911085858816junit45 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 45s of 1h3m1s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319128191503175680junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m11s of 58m56s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319037322288697344junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m9s of 57m59s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318946466445660160junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m9s of 1h16m44s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318855786268463104junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m15s of 1h9m40s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318764929515261952junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m17s of 1h5m1s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318674079506501632junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 52s of 1h3m0s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318583241577336832junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 55s of 1h2m0s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318492512746213376junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m27s of 1h5m20s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318401645893128192junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 44s of 1h3m3s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318310794131148800junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 39s of 1h6m18s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
release-openshift-origin-installer-e2e-gcp-ovn-upgrade-4.5-stable-to-4.6-ci - 21 runs, 100% failed, 76% of failures match
#1319841181512765440junit3 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m34s of 2h32m12s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319750334733619200junit9 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 11s of 1h35m34s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319659603218141184junit14 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 12s of 2h33m25s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319568724042190848junit22 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 39s of 1h37m35s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319387059672059904junit33 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 30s of 2h32m15s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319296232832634880junit40 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 47s of 1h36m4s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319114585923391488junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 47s of 2h32m19s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319023744684920832junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 52s of 2h32m21s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318842190994083840junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m5s of 1h38m11s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318751339332767744junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m30s of 1h33m28s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318660486006312960junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 16s of 1h36m38s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318569667924594688junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 37s of 2h32m9s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318478913202032640junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 44s of 2h32m16s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318388053810614272junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 24s of 1h30m12s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318297198844186624junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m30s of 2h32m16s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317404959897030656junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m32s of 2h32m20s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
release-openshift-origin-installer-e2e-azure-upgrade-4.5-stable-to-4.6-ci - 21 runs, 62% failed, 108% of failures match
#1319841672384745472junit3 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3s of 1h16m0s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319750829565022208junit10 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 14s of 1h3m31s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319660075761012736junit16 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 22s of 1h9m24s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319569229271273472junit21 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h8m38s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319478376964034560junit27 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 8s of 1h8m7s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319387567786823680junit33 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 5s of 1h11m9s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319205955400896512junit46 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h5m52s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319115090879844352junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 1h18m15s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318933472538005504junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 1h10m34s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318842699247259648junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 56s of 1h8m43s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318570170624512000junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3s of 1h9m1s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318479414819819520junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 5s of 1h7m14s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318388556426645504junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3m4s of 1h7m13s (5%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317428364130127872junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 1h12m32s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
release-openshift-origin-installer-e2e-azure-upgrade-4.4-stable-to-4.5-ci - 21 runs, 57% failed, 117% of failures match
#1319841672342802432junit4 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3s of 1h2m2s (0%):
#1319750829497913344junit9 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3s of 1h7m30s (0%):
#1319660075568074752junit15 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h5m39s (0%):
#1319569229178998784junit22 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 1h6m44s (0%):
#1319478376926285824junit28 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 59m43s (0%):
#1319115090804346880junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h0m13s (0%):
#1319024253391081472junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 5s of 59m38s (0%):
#1318933472525422592junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h0m1s (0%):
#1318842699209510912junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 55m44s (0%):
#1318660989800943616junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m21s of 1h2m35s (2%):
#1318570170620317696junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 1h6m58s (0%):
#1318479414790459392junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m56s of 1h1m38s (3%):
#1318388556376313856junit4 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 16s of 1h2m44s (0%):
#1317425092942106624junit6 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 58m54s (0%):
release-openshift-origin-installer-e2e-azure-upgrade-4.5 - 21 runs, 76% failed, 63% of failures match
#1319841672300859392junit4 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 38m37s (0%):
#1319660075547103232junit16 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3s of 49m3s (0%):
#1319568986895028224junit22 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m5s of 53m42s (2%):
#1319478118771068928junit28 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 47m11s (0%):
#1319387304179011584junit34 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m27s of 44m6s (3%):
#1319205710130581504junit46 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m39s of 41m50s (6%):
#1319114836579192832junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 44m19s (0%):
#1318660739438743552junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 20s of 35m12s (1%):
#1318479162901532672junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 36m11s (0%):
#1318388305942810624junit4 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 1h17m26s (0%):
release-openshift-origin-installer-e2e-azure-ovn-upgrade-4.5-stable-to-4.6-ci - 20 runs, 100% failed, 80% of failures match
#1319802416064892928junit5 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 19m52s of 2h31m41s (13%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319711697665003520junit11 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m37s of 2h32m5s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319439125765427200junit29 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m12s of 2h1m38s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319348267661660160junit36 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 18s of 1h37m2s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319257413466984448junit41 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m22s of 1h54m43s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319166703678001152junit47 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m12s of 2h31m52s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319075821612175360junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m49s of 1h53m30s (2%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318984978092003328junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m50s of 2h37m16s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318894198815985664junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 9m21s of 2h32m32s (6%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318803435616735232junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m33s of 1h54m25s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318621738564587520junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 31s of 2h32m15s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318530924652007424junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m42s of 2h0m24s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318440148874039296junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m48s of 2h32m24s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318349299322458112junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m1s of 2h32m29s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317440946454925312junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m4s of 2h32m10s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317350097876422656junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 9m29s of 2h32m34s (6%), this is currently sufficient to pass the test/job but not considered completely correct:
release-openshift-origin-installer-e2e-gcp-upgrade-4.4-stable-to-4.5-ci - 21 runs, 38% failed, 163% of failures match
#1319751082208923648junit10 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m14s of 51m18s (2%):
#1319569479457312768junit22 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m28s of 48m39s (3%):
#1319387834074796032junit34 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m18s of 50m12s (3%):
#1319296976843444224junit40 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 51s of 50m38s (2%):
#1319206208548114432junit46 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m21s of 52m41s (3%):
#1319115338285060096junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m0s of 50m27s (2%):
#1318933728730288128junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 58s of 53m39s (2%):
#1318752094554951680junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m41s of 56m17s (3%):
#1318661242256101376junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 48s of 55m6s (1%):
#1318479669091110912junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m9s of 54m33s (2%):
#1318388809947156480junit4 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m17s of 48m41s (3%):
#1318297956088025088junit4 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 35s of 47m41s (1%):
#1317425344013144064junit6 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m12s of 48m8s (2%):
pull-ci-openshift-origin-release-4.5-e2e-gcp-upgrade - 13 runs, 15% failed, 500% of failures match
#1319716808923549696junit12 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 58s of 32m53s (3%):
#1319699245011308544junit13 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m32s of 34m53s (4%):
#1319661910425079808junit16 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m2s of 34m8s (3%):
#1319586941573795840junit21 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m7s of 33m43s (3%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319286756117319680junit41 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 37s of 33m44s (2%):
#1319278806615199744junit41 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m24s of 33m50s (4%):
#1319022513065299968junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m6s of 32m25s (3%):
#1319005232096612352junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 42s of 32m43s (2%):
#1318991656770342912junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m27s of 33m24s (4%):
#1318939470598246400junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m14s of 30m49s (4%):
release-openshift-origin-installer-old-rhcos-e2e-aws-4.5 - 2 runs, 100% failed, 150% of failures match
#1316505466439733248junit13 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3s of 26m48s (0%):
#1319405446783569920junit33 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 44m14s (0%):
#1318680368890515456junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 9s of 38m48s (0%):
rehearse-13019-release-openshift-origin-installer-e2e-aws-upgrade-4.4-to-4.5-to-4.6-to-4.7-ci - 3 runs, 100% failed, 33% of failures match
#1319683725352505344junit12 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m26s of 3h4m55s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
pull-ci-openshift-ovn-kubernetes-release-4.5-e2e-gcp-ovn-upgrade - 5 runs, 40% failed, 150% of failures match
#1319664374700314624junit13 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 21s of 34m12s (1%):
#1319017621621837824junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 10s of 33m29s (0%):
#1318291014682677248junit4 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 17s of 32m38s (1%):
rehearse-12061-release-openshift-origin-installer-e2e-aws-upgrade-4.5-with-caps-patch-to-4.6 - 5 runs, 0% failed, 40% of runs match
#1319669618729553920junit15 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 29s of 1h9m35s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318529561771642880junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 58s of 1h10m6s (1%), this is currently sufficient to pass the test/job but not considered completely correct:
pull-ci-openshift-cluster-etcd-operator-release-4.5-e2e-agnostic-upgrade - 6 runs, 83% failed, 20% of failures match
#1319675314766352384junit15 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m19s of 33m45s (4%):
release-openshift-origin-installer-e2e-gcp-upgrade-4.5 - 3 runs, 0% failed, 100% of runs match
#1319636641714802688junit18 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m0s of 32m8s (3%):
#1318911566350913536junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m31s of 28m43s (5%):
#1317461581948260352junit6 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m5s of 28m33s (4%):
release-openshift-origin-installer-e2e-azure-ovn-upgrade-4.4-stable-to-4.5-ci - 20 runs, 75% failed, 60% of failures match
#1319620788155846656junit18 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m8s of 1h10m43s (2%):
#1319529959290572800junit24 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m9s of 1h1m25s (2%):
#1319439125685735424junit30 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4m9s of 1h14m8s (6%):
#1319348267615522816junit36 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m40s of 1h15m20s (2%):
#1319075821578620928junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 57s of 1h7m33s (1%):
#1318984978029088768junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 53s of 1h2m18s (1%):
#1318803435578986496junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m40s of 1h7m14s (2%):
#1318621738514255872junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 31s of 1h5m48s (1%):
#1318530924605870080junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 42s of 1h10m11s (1%):
pull-ci-operator-framework-operator-lifecycle-manager-release-4.5-e2e-upgrade - 3 runs, 33% failed, 200% of failures match
#1319596716160192512junit21 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 34s of 31m13s (2%):
#1318997403377864704junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 55s of 30m31s (3%):
rehearse-12789-pull-ci-openshift-cluster-version-operator-release-4.5-e2e-agnostic-upgrade - 1 runs, 0% failed, 100% of runs match
#1319564350142287872junit22 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m46s of 57m33s (5%):
release-openshift-origin-installer-e2e-aws-upgrade-4.2-to-4.3-to-4.4-to-4.5-ci - 5 runs, 40% failed, 250% of failures match
#1319522412059955200junit23 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 11m51s of 2h45m48s (7%):
#1319159909509500928junit47 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 12m6s of 2h34m16s (8%):
#1318797397861601280junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 10m22s of 2h33m35s (7%):
#1318434863556071424junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 11m6s of 2h32m31s (7%):
#1317347078107566080junit6 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 14m46s of 2h47m42s (9%):
pull-ci-openshift-machine-config-operator-release-4.5-e2e-agnostic-upgrade - 6 runs, 33% failed, 200% of failures match
#1319492838207000576junit27 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 38s of 33m41s (2%):
#1319493252327411712junit27 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m25s of 27m54s (5%):
#1319493194680897536junit27 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m3s of 32m13s (3%):
#1319494744610443264junit27 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 50s of 29m26s (3%):
pull-ci-openshift-console-operator-release-4.5-e2e-agnostic-upgrade - 1 runs, 0% failed, 100% of runs match
#1319491390782050304junit27 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m11s of 30m1s (4%):
pull-ci-openshift-cluster-network-operator-release-4.5-e2e-agnostic-upgrade - 4 runs, 50% failed, 150% of failures match
#1319474211026112512junit28 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 48s of 28m51s (3%):
#1319473691548979200junit28 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 41s of 29m31s (2%):
#1319474660756164608junit28 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 45s of 34m11s (2%):
release-openshift-origin-installer-e2e-aws-upgrade-4.3-to-4.4-to-4.5-to-4.6-ci - 5 runs, 20% failed, 400% of failures match
#1319434108484456448junit29 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 10m16s of 2h42m49s (6%), this is currently sufficient to pass the test/job but not considered completely correct:
#1319071552125276160junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 10m48s of 2h50m36s (6%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318709056830967808junit3 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 11m59s of 2h50m18s (7%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318346531706769408junit4 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 9m6s of 2h45m12s (6%), this is currently sufficient to pass the test/job but not considered completely correct:
pull-ci-openshift-machine-config-operator-release-4.5-e2e-upgrade - 1 runs, 0% failed, 100% of runs match
#1319374204201603072junit35 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 54s of 30m5s (3%):
release-openshift-origin-installer-e2e-aws-ovn-upgrade-4.4-stable-to-4.5-ci - 2 runs, 0% failed, 100% of runs match
#1319323112017235968junit38 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 5s of 1h5m20s (0%):
#1318598092928323584junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4s of 58m3s (0%):
release-openshift-ocp-installer-e2e-ovirt-upgrade-4.4-stable-to-4.5-ci - 2 runs, 100% failed, 100% of failures match
#1319270004436242432junit41 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 4m5s of 1h21m13s (5%):
#1318545000421658624junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m41s of 1h16m18s (4%):
rehearse-12789-pull-ci-openshift-cluster-version-operator-release-4.5-e2e-rollback - 4 runs, 75% failed, 33% of failures match
#1319293235956289536junit40 hours ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2m52s of 52m26s (5%):
release-openshift-ocp-installer-e2e-ovirt-upgrade-4.5-stable-to-4.6-ci - 10 runs, 50% failed, 60% of failures match
#1319227974167302144junit44 hours ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 11s of 1h3m25s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1318865354964865024junit2 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 1h3m32s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
#1317414019912437760junit6 days ago
# [sig-network-edge] Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 19s of 1h28m20s (0%), this is currently sufficient to pass the test/job but not considered completely correct:
pull-ci-openshift-cluster-etcd-operator-release-4.5-e2e-upgrade - 2 runs, 0% failed, 100% of runs match
#1319100603531530240junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1m0s of 27m52s (4%):
#1318996597073252352junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 49s of 29m21s (3%):
pull-ci-openshift-oc-release-4.5-e2e-aws-upgrade - 1 runs, 0% failed, 100% of runs match
#1319017621709918208junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 3s of 33m42s (0%):
pull-ci-openshift-router-release-4.5-e2e-aws-upgrade - 4 runs, 50% failed, 50% of failures match
#1319000705654067200junit2 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 42s of 34m41s (2%):
release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.5 - 5 runs, 40% failed, 50% of failures match
#1318658729926725632junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 2s of 19m59s (0%):
pull-ci-openshift-cluster-network-operator-release-4.5-e2e-upgrade - 1 runs, 0% failed, 100% of runs match
#1318584974781190144junit3 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 59s of 30m18s (3%):
pull-ci-openshift-cluster-kube-scheduler-operator-release-4.5-e2e-upgrade - 4 runs, 75% failed, 33% of failures match
#1317399783215730688junit6 days ago
# Cluster frontend ingress remain available
Frontends were unreachable during disruption for at least 1s of 1h17m32s (0%):

Across 3999 runs and 290 jobs (57.16% failed), matched 10.76% of failing runs and 12.41% of jobs in 107ms - clear search | chart view - source code located on github