kubernetes: [k8s.io] Service endpoints latency should not be very high [Conformance] {Kubernetes e2e suite}
Failed: [k8s.io] Service endpoints latency should not be very high [Conformance] {Kubernetes e2e suite}
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service_latency.go:115
Not all RC/pod/service trials succeeded: got 1 errors
50, 90, 99 percentiles: 2.294165339s 2.435644323s 2.953528631s
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service_latency.go:113
Happened on a presubmit run in #30625.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 40 (38 by maintainers)
Indeed the service latency test may hang if
nodeNameis happens to be e.g.172.17.0.6due to #31311 because dots makenodeNamean invalid DNS1123Label. You get the following diagnostics in controller manager log in this case:E0904 19:58:31.919368 1 endpoints_controller.go:514] Endpoints “kubernetes-dashboard” is invalid: [subsets[0].addresses[0].nodeName: Invalid value: “172.17.0.6”: must match the regex a-z0-9? (e.g. ‘my-name’ or ‘123-abc’), subsets[0].addresses[0].nodeName: Invalid value: “172.17.0.6”: must match the regex a-z0-9? (e.g. ‘my-name’ or ‘123-abc’)]