Job:
#1968079bug7 months agoGCP CI: dial tcp: lookup api... on 172.30.0.10:53: no such host CLOSED
  [sig-api-machinery] kube-apiserver-new-connection should be available
  Run #0: Failed expand_less	51m58s
#1887509bug11 months agoOpenshift-tests conformance TopologyManager tests run when Machine Config Operator is not installed on cluster RELEASE_PENDING
passed: [sig-network] pods should successfully create sandboxes by other
passed: [sig-api-machinery] kube-apiserver-new-connection should be available
passed: [sig-api-machinery] openshift-apiserver-new-connection should be available
passed: [sig-api-machinery] oauth-apiserver-new-connection should be available
passed: [sig-api-machinery] kube-apiserver-reused-connection should be available
passed: [sig-api-machinery] openshift-apiserver-reused-connection should be available
passed: [sig-api-machinery] oauth-apiserver-reused-connection should be available
(duplicates are used to mark some failures as flake and not to fail the whole suite
periodic-ci-openshift-release-master-ci-4.10-upgrade-from-stable-4.9-e2e-gcp-ovn-upgrade (all) - 490 runs, 64% failed, 19% of failures match = 12% impact
#1484898329283268608junit10 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 46m23s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 46m23s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 46m23s)
#1484837853228699648junit14 hours ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484837853228699648junit14 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 48m8s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 48m8s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 48m8s)
#1484837855753670656junit14 hours ago
[bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484837855753670656junit14 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 37m41s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 5s seconds (test duration: 37m41s)
#1484610294931001344junit29 hours ago
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 40m59s)
#1484610294037614592junit29 hours ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484610294037614592junit29 hours ago
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 1s seconds (test duration: 45m55s)
#1484610293316194304junit29 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 48m24s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 48m24s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 48m24s)
#1484610296612917248junit29 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 4s seconds (test duration: 39m41s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 4s seconds (test duration: 39m41s)
#1484610295769862144junit29 hours ago
ending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484610295769862144junit29 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 49m43s)
#1484356682984198144junit46 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 45m58s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 45m58s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 1s seconds (test duration: 45m58s)
#1484080913921871872junit2 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484080913921871872junit2 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 47m0s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 47m0s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 47m0s)
#1484206535402852352junit2 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484206535402852352junit2 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 35m38s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 35m38s)
#1484008270115901440junit2 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 51m29s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 51m29s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 51m29s)
#1484008266844344320junit2 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484008266844344320junit2 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 45m56s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 45m56s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 45m56s)
#1484008265179205632junit2 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484008265179205632junit2 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 4s seconds (test duration: 35m56s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 35m56s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 35m56s)
#1484008270950567936junit2 days ago
[bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484008270950567936junit2 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 4s seconds (test duration: 33m26s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 4s seconds (test duration: 33m26s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 5s seconds (test duration: 33m26s)
#1483916966920982528junit3 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1483916966920982528junit3 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 49m7s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 4s seconds (test duration: 49m7s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 49m7s)
#1483916974479118336junit3 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 34m8s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 34m8s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 1s seconds (test duration: 34m8s)
#1483666887005966336junit3 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1483666887005966336junit3 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 39m48s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 39m48s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 39m48s)
#1483760924115341312junit3 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 32m56s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 32m56s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 32m56s)
#1483609924863791104junit4 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1483609924863791104junit4 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 37m52s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 37m52s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 37m52s)
#1483543700880494592junit4 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 6s seconds (test duration: 36m59s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 36m59s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 5s seconds (test duration: 36m59s)
#1483300478811901952junit4 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 41m8s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 41m8s)
#1483207426688684032junit5 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1483207426688684032junit5 days ago
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 35m48s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 35m48s)
#1483068564532367360junit5 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1483068564532367360junit5 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 4s seconds (test duration: 38m3s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 38m3s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 38m3s)
#1482905390168412160junit5 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 39m2s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 39m2s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 39m2s)
#1482905391833550848junit5 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 41m41s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 41m41s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 41m41s)
#1482797166459097088junit6 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 4s seconds (test duration: 50m41s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 50m41s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 50m41s)
#1482421196749279232junit7 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 4s seconds (test duration: 36m38s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 4s seconds (test duration: 36m38s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 36m38s)
#1482283894978908160junit7 days ago
[bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above pending
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1482283894978908160junit7 days ago
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 33m22s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 33m22s)
#1482186657774964736junit7 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 41m5s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 41m5s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 41m5s)
#1482095252398411776junit8 days ago
[bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1482095252398411776junit8 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 35m57s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 4s seconds (test duration: 35m57s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 35m57s)
#1482029692780285952junit8 days ago
[bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1482029692780285952junit8 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 41m29s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 41m29s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 41m29s)
#1481935339978231808junit8 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 49m43s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 4s seconds (test duration: 49m43s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 49m43s)
#1481864279144534016junit8 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 30m42s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 30m42s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 30m42s)
#1481864280847421440junit8 days ago
[bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1481864280847421440junit8 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 35m3s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 35m3s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 35m3s)
#1481806783142957056junit8 days ago
[bz-storage][invariant] alert/KubePersistentVolumeErrors should not be at or above pending
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1481806783142957056junit8 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 34m53s)
#1481715380782108672junit9 days ago
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1481715380782108672junit9 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 37m3s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 5s seconds (test duration: 37m3s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 5s seconds (test duration: 37m3s)
#1481416903535628288junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 33m23s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 33m23s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 6s seconds (test duration: 33m23s)
#1481352958741319680junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 38m48s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 38m48s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 38m48s)
#1481352952026238976junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 43m23s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 43m23s)
#1481352957063598080junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 38m46s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 38m46s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 38m46s)
#1481290774409646080junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 32m35s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 32m35s)
#1481224067565490176junit10 days ago
[bz-Management Console] clusteroperator/console should not change condition/Available
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1481224067565490176junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 33m2s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 4s seconds (test duration: 33m2s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 33m2s)
#1481224068404350976junit10 days ago
[bz-apiserver-auth] clusteroperator/authentication should not change condition/Available
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1481224068404350976junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 43m17s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 43m17s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 43m17s)
#1481167080219742208junit10 days ago
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1481167080219742208junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 46m33s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 46m33s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 1s seconds (test duration: 46m33s)
#1481167074708426752junit10 days ago
ew should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1481167074708426752junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 39m24s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 39m24s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 39m24s)
#1481107806068150272junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 40m5s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 40m5s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 1s seconds (test duration: 40m5s)
#1481048900381970432junit11 days ago
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1481048900381970432junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 39m8s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 5s seconds (test duration: 39m8s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 7s seconds (test duration: 39m8s)
#1481048897026527232junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 35m26s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 35m26s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 35m26s)
#1480795454718349312junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 37m14s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 37m14s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 3s seconds (test duration: 37m14s)
#1480795451358711808junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 38m30s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 38m30s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 38m30s)
#1481048899954151424junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 43m53s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 21s seconds (test duration: 43m53s)
# [sig-api-machinery] disruption/oauth-api connection/reused should be available throughout the test
disruption/oauth-api connection/reused was failing for 17s seconds (test duration: 43m53s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 20s seconds (test duration: 43m53s)
# [sig-api-machinery] disruption/openshift-api connection/reused should be available throughout the test
disruption/openshift-api connection/reused was failing for 20s seconds (test duration: 43m53s)
#1480795453900460032junit11 days ago
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1480795453900460032junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 40m33s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 40m33s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 1s seconds (test duration: 40m33s)
#1480719273486716928junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 4s seconds (test duration: 45m35s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 45m35s)
#1480719268470329344junit11 days ago
[bz-Management Console] clusteroperator/console should not change condition/Available
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1480719268470329344junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 3s seconds (test duration: 38m1s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 5s seconds (test duration: 38m1s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 38m1s)
#1480552825137139712junit12 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 40m21s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 2s seconds (test duration: 40m21s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 1s seconds (test duration: 40m21s)
#1480552822729609216junit12 days ago
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1480552822729609216junit12 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 1s seconds (test duration: 34m38s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 1s seconds (test duration: 34m38s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 34m38s)
#1480485102482886656junit12 days ago
[bz-apiserver-auth] clusteroperator/authentication should not change condition/Available
[sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
[sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
[sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1480485102482886656junit12 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 5s seconds (test duration: 38m2s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 5s seconds (test duration: 38m2s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 4s seconds (test duration: 38m2s)
#1480268735175462912junit13 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 2s seconds (test duration: 34m58s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 3s seconds (test duration: 34m58s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 2s seconds (test duration: 34m58s)

Found in 12.04% of runs (18.79% of failures) across 490 total runs and 1 jobs (64.08% failed) in 133ms - clear search | chart view - source code located on github