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
pull-ci-openshift-ovn-kubernetes-master-e2e-gcp-ovn (all) - 100 runs, 47% failed, 28% of failures match = 13% impact
#1484584439022358528junit32 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: 40m51s)
# [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: 40m51s)
# [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: 40m51s)
#1484450134262550528junit41 hours ago
t
[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
#1484450134262550528junit41 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: 48m55s)
# [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: 48m55s)
# [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: 48m55s)
#1484290515410096128junit2 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: 36m1s)
# [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: 36m1s)
# [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: 36m1s)
#1483933047437922304junit3 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
#1483933047437922304junit3 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: 33m38s)
# [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: 33m38s)
# [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: 33m38s)
#1483889255846514688junit3 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: 32m35s)
# [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: 32m35s)
# [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: 32m35s)
#1483885760640716800junit3 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-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
#1483885760640716800junit3 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: 32m17s)
# [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: 32m17s)
# [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: 32m17s)
#1483259369150746624junit5 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: 41m56s)
# [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: 41m56s)
# [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: 41m56s)
#1481744483899936768junit9 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: 31m59s)
# [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: 31m59s)
# [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: 31m59s)
#1482093466870616064junit8 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: 35m46s)
# [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: 35m46s)
# [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: 35m46s)
#1481313828980396032junit10 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 11s seconds (test duration: 34m11s)
# [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: 34m11s)
# [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: 34m11s)
#1480228948523618304junit13 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: 38m12s)
# [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: 38m12s)
#1480987755751149568junit11 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: 33m4s)
# [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: 33m4s)
# [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: 33m4s)
#1481006039326265344junit11 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 8s seconds (test duration: 46m9s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 34s seconds (test duration: 46m9s)
# [sig-api-machinery] disruption/oauth-api connection/reused should be available throughout the test
disruption/oauth-api connection/reused was failing for 32s seconds (test duration: 46m9s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 26s seconds (test duration: 46m9s)
# [sig-api-machinery] disruption/openshift-api connection/reused should be available throughout the test
disruption/openshift-api connection/reused was failing for 33s seconds (test duration: 46m9s)

Found in 13.00% of runs (27.66% of failures) across 100 total runs and 1 jobs (47.00% failed) in 139ms - clear search | chart view - source code located on github