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-nightly-4.10-e2e-vsphere-serial (all) - 83 runs, 52% failed, 7% of failures match = 4% impact
#1484777468559626240junit18 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: 42m20s)
# [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: 42m20s)
# [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: 42m20s)
#1484669308993802240junit25 hours ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 9s seconds (test duration: 53m52s)
# [sig-api-machinery] disruption/kube-api connection/reused should be available throughout the test
disruption/kube-api connection/reused was failing for 6s seconds (test duration: 53m52s)
# [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: 53m52s)
# [sig-api-machinery] disruption/oauth-api connection/reused should be available throughout the test
disruption/oauth-api connection/reused was failing for 5s seconds (test duration: 53m52s)
# [sig-api-machinery] disruption/openshift-api connection/new should be available throughout the test
disruption/openshift-api connection/new was failing for 8s seconds (test duration: 53m52s)

... 3 lines not shown

#1483207382308753408junit5 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/oauth-api connection/reused 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
#1483207382308753408junit5 days ago
# [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test
disruption/kube-api connection/new was failing for 9s seconds (test duration: 54m38s)
# [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: 54m38s)

Found in 3.61% of runs (6.98% of failures) across 83 total runs and 1 jobs (51.81% failed) in 236ms - clear search | chart view - source code located on github