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-nightly-4.10-e2e-vsphere (all) - 86 runs, 44% failed, 8% of failures match = 3% impact
#1484610331899596800junit29 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: 33m32s)
# [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: 33m32s)
# [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: 33m32s)
#1484667225603313664junit25 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 12s seconds (test duration: 32m4s)
# [sig-api-machinery] disruption/kube-api connection/reused should be available throughout the test
disruption/kube-api connection/reused was failing for 2s seconds (test duration: 32m4s)
# [sig-api-machinery] disruption/oauth-api connection/new should be available throughout the test
disruption/oauth-api connection/new was failing for 12s seconds (test duration: 32m4s)
# [sig-api-machinery] disruption/oauth-api connection/reused should be available throughout the test
disruption/oauth-api connection/reused was failing for 3s seconds (test duration: 32m4s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 12s seconds (test duration: 32m4s)
#1483144457535623168junit5 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
#1483144457535623168junit5 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: 25m39s)
# [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: 25m39s)
# [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: 25m39s)

Found in 3.49% of runs (7.89% of failures) across 86 total runs and 1 jobs (44.19% failed) in 208ms - clear search | chart view - source code located on github