Job:
#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
#1968079bug7 months agoGCP CI: dial tcp: lookup api... on 172.30.0.10:53: no such host NEW
  [sig-api-machinery] kube-apiserver-new-connection should be available
  Run #0: Failed expand_less	51m58s
periodic-ci-openshift-release-master-ci-4.10-e2e-gcp-upgrade (all) - 957 runs, 57% failed, 18% of failures match = 10% impact
#1485031297653936128junit21 minutes 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: 41m1s)
# [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: 41m1s)
# [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: 41m1s)
#1484918028087857152junit8 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-api-machinery] disruption/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484918028087857152junit8 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: 46m51s)
# [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: 46m51s)
# [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: 46m51s)
#1484684029537030144junit23 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: 41m47s)
# [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: 41m47s)
# [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: 41m47s)
#1484626162142416896junit27 hours 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
#1484626162142416896junit27 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: 34m20s)
# [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: 34m20s)
#1484684028689780736junit24 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: 36m9s)
# [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: 36m9s)
#1484626161307750400junit27 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: 36m33s)
# [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: 36m33s)
# [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: 36m33s)
#1484560712012402688junit31 hours ago
# [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: 42m41s)
# [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: 42m41s)
#1484626164898074624junit27 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: 42m30s)
#1484626162985472000junit27 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: 39m23s)
#1484560711156764672junit32 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/openshift-api connection/new should be available throughout the test
[sig-arch] Monitor cluster while tests execute
#1484560711156764672junit32 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: 42m1s)
# [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: 42m1s)
#1484378376754958336junit44 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
#1484378376754958336junit44 hours 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: 39m24s)
# [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: 39m24s)
# [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: 39m24s)
#1484378374242570240junit44 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: 40m57s)
# [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: 40m57s)
# [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: 40m57s)
#1484495207159304192junit36 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: 36m42s)
# [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: 36m42s)
# [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: 36m42s)
#1484324423472254976junit47 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: 43m26s)
# [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: 43m26s)
# [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: 43m26s)
#1484324426005614592junit47 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
#1484324426005614592junit47 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: 36m5s)
# [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: 36m5s)
# [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: 36m5s)
#1484077568389812224junit2 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: 41m53s)
# [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: 41m53s)
# [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: 41m53s)
#1484139591978979328junit2 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: 34m14s)
# [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: 34m14s)
# [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: 34m14s)
#1484015679488135168junit2 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: 33m41s)
# [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: 33m41s)
# [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: 33m41s)
#1483961743666319360junit2 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-arch] Monitor cluster while tests execute
#1483961743666319360junit2 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: 36m18s)
# [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: 36m18s)
#1483844845486215168junit3 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: 31m50s)
# [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: 31m50s)
# [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: 31m50s)
#1483844852192907264junit3 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
#1483844852192907264junit3 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: 36m12s)
# [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: 36m12s)
# [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: 36m12s)
#1483742821075652608junit3 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
#1483742821075652608junit3 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: 35m0s)
# [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: 35m0s)
# [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: 35m0s)
#1483584247255011328junit4 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
#1483584247255011328junit4 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: 40m32s)
# [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: 40m32s)
# [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: 40m32s)
#1483533881440210944junit4 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-arch] Monitor cluster while tests execute
#1483533881440210944junit4 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: 34m21s)
# [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: 34m21s)
#1483533879745712128junit4 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: 33m32s)
#1483467685957210112junit4 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: 37m59s)
# [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: 37m59s)
# [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: 37m59s)
#1483373141936836608junit4 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
#1483373141936836608junit4 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: 42m59s)
# [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: 42m59s)
# [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: 42m59s)
#1483373137029500928junit4 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: 34m34s)
# [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: 34m34s)
#1483320347942981632junit4 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
#1483320347942981632junit4 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: 32m51s)
# [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: 32m51s)
# [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: 32m51s)
#1483199472455389184junit5 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
#1483199472455389184junit5 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: 38m9s)
# [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: 38m9s)
# [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: 38m9s)
#1483254877046968320junit4 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
#1483254877046968320junit4 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: 35m21s)
# [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: 35m21s)
# [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: 35m21s)
#1483040906843000832junit5 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
#1483040906843000832junit5 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: 30m36s)
# [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: 30m36s)
# [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: 30m36s)
#1482940268658298880junit5 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: 33m12s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 7s seconds (test duration: 33m12s)
# [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: 33m12s)
#1482884866834960384junit5 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
#1482884866834960384junit5 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: 39m33s)
# [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: 39m33s)
# [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: 39m33s)
#1482827021368168448junit6 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: 35m29s)
# [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: 35m29s)
# [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: 35m29s)
#1482826998484045824junit6 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
#1482826998484045824junit6 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: 30m33s)
# [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: 30m33s)
# [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: 30m33s)
#1482761529852956672junit6 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: 34m1s)
# [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: 34m1s)
# [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: 34m1s)
#1482761527327985664junit6 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
#1482761527327985664junit6 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: 35m57s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 6s 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 6s seconds (test duration: 35m57s)
#1482711256895852544junit6 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
#1482711256895852544junit6 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: 31m52s)
# [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: 31m52s)
# [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: 31m52s)
#1482660902925766656junit6 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: 32m27s)
# [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: 32m27s)
# [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: 32m27s)
#1482660895376019456junit6 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: 30m51s)
# [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: 30m51s)
# [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: 30m51s)
#1482660896210685952junit6 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: 35m27s)
# [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: 35m27s)
# [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: 35m27s)
#1482349034243887104junit7 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: 50m33s)
# [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: 50m33s)
#1482301108339609600junit7 days 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: 39m15s)
#1482240640191303680junit7 days ago
# [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: 36m33s)
# [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: 36m33s)
#1482301110898135040junit7 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: 35m38s)
#1482240640463933440junit7 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: 33m12s)
# [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: 33m12s)
# [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: 33m12s)
#1482051172322775040junit8 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
#1482051172322775040junit8 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: 34m52s)
# [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: 34m52s)
#1482051169013469184junit8 days ago
auth-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
#1482051169013469184junit8 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: 32m42s)
# [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: 32m42s)
# [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: 32m42s)
#1482051174008885248junit8 days 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: 42m13s)
#1482051178429681664junit8 days ago
[bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn 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
#1482051178429681664junit8 days 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: 32m41s)
#1481985639325896704junit8 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
#1481985639325896704junit8 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: 32m2s)
# [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: 32m2s)
# [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: 32m2s)
#1481941205519437824junit8 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: 36m5s)
# [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: 36m5s)
#1481941207197159424junit8 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
#1481941207197159424junit8 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: 29m59s)
# [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: 29m59s)
# [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: 29m59s)
#1481838029575294976junit8 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: 46m5s)
# [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: 46m5s)
# [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: 46m5s)
#1481838032087683072junit8 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
#1481838032087683072junit8 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: 43m42s)
# [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: 43m42s)
# [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: 43m42s)
#1481787664385445888junit8 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
#1481787664385445888junit8 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: 34m4s)
#1481787667745083392junit8 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
#1481787667745083392junit8 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: 33m15s)
# [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: 33m15s)
# [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: 33m15s)
#1481787666922999808junit8 days ago
# [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: 54m40s)
# [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: 54m40s)
#1481737401368842240junit9 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: 38m1s)
# [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: 38m1s)
# [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: 38m1s)
#1481787669422804992junit8 days ago
[bz-kube-apiserver][invariant] alert/KubeClientErrors 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
#1481787669422804992junit8 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: 33m46s)
#1481787665232695296junit8 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 7s seconds (test duration: 32m51s)
# [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: 32m51s)
# [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: 32m51s)
#1481688220960821248junit9 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
#1481688220960821248junit9 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: 35m30s)
# [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: 35m30s)
# [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: 35m30s)
#1481629853324152832junit9 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: 37m21s)
# [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: 37m21s)
# [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: 37m21s)
#1481629855769432064junit9 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: 35m11s)
# [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: 35m11s)
# [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: 35m11s)
#1481629854938959872junit9 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: 32m50s)
# [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: 32m50s)
# [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: 32m50s)
#1481629853521285120junit9 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
#1481629853521285120junit9 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: 34m51s)
# [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: 34m51s)
# [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: 34m51s)
#1477642881828130816junit9 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: 27m17s)
# [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: 27m17s)
# [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: 27m17s)
#1481506620344111104junit9 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: 32m47s)
# [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: 32m47s)
# [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: 32m47s)
#1481506621182971904junit9 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
#1481506621182971904junit9 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: 29m37s)
# [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: 29m37s)
# [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: 29m37s)
#1481441090463600640junit9 days ago
# [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: 31m57s)
# [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: 31m57s)
#1481385750007123968junit10 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
#1481385750007123968junit10 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: 33m27s)
# [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: 33m27s)
# [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: 33m27s)
#1481332906595979264junit10 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
#1481332906595979264junit10 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: 35m11s)
# [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: 35m11s)
# [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: 35m11s)
#1481232184395173888junit10 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-arch] Monitor cluster while tests execute
#1481232184395173888junit10 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: 31m41s)
# [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: 31m41s)
#1481111464822444032junit10 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
#1481111464822444032junit10 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: 36m21s)
# [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: 36m21s)
# [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: 36m21s)
#1481176840327401472junit10 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: 32m10s)
# [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: 32m10s)
# [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: 32m10s)
#1481111467322249216junit10 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
#1481111467322249216junit10 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: 36m11s)
# [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: 36m11s)
# [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: 36m11s)
#1481111462284890112junit10 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
#1481111462284890112junit10 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: 31m18s)
# [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: 31m18s)
# [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: 31m18s)
#1481058647546007552junit11 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: 32m25s)
# [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: 32m25s)
# [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: 32m25s)
#1481058641690759168junit11 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: 33m46s)
# [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: 33m46s)
# [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: 33m46s)
#1480899954238033920junit11 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: 38m45s)
# [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: 38m45s)
#1480899951868252160junit11 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
#1480899951868252160junit11 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: 33m46s)
# [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: 33m46s)
# [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: 33m46s)
#1480706220930109440junit11 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-arch] Monitor cluster while tests execute
#1480706220930109440junit11 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: 34m22s)
#1480603383822815232junit12 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: 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)
#1480603385513119744junit12 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: 37m17s)
# [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: 37m17s)
# [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: 37m17s)
#1480555315169595392junit12 days ago
[sig-api-machinery] disruption/kube-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
#1480555315169595392junit12 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: 36m13s)
# [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: 36m13s)
#1480500161976209408junit12 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-arch] Monitor cluster while tests execute
#1480500161976209408junit12 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: 33m59s)
# [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: 33m59s)
#1480396693965901824junit12 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: 34m14s)
# [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: 34m14s)
# [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: 34m14s)
#1480396685556322304junit12 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
#1480396685556322304junit12 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: 31m46s)
# [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: 31m46s)
# [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: 31m46s)
#1480396694775402496junit12 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
#1480396694775402496junit12 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: 35m10s)
# [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: 35m10s)
# [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: 35m10s)
#1480341270227324928junit12 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: 41m40s)
# [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: 41m40s)
# [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: 41m40s)
#1480240647578324992junit13 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: 40m54s)
# [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: 40m54s)
# [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: 40m54s)
#1480175208387055616junit13 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: 32m52s)
# [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: 32m52s)
# [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: 32m52s)
#1480127397490593792junit13 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
#1480127397490593792junit13 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: 34m1s)
# [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: 34m1s)
# [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: 34m1s)
#1480016644502720512junit13 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
#1480016644502720512junit13 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: 34m2s)
# [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: 34m2s)
# [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: 34m2s)

Found in 9.93% of runs (17.56% of failures) across 957 total runs and 1 jobs (56.53% failed) in 163ms - clear search | chart view - source code located on github