Inaccurate error message when cluster EOFs

[ewdurbin]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

• EOF
• multiple kinds
• falling back to hardcoded types

Kubernetes version (use kubectl version):

tested two version:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T21:12:46Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Unable to connect to the server: EOF

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-09T21:51:54Z", GoVersion:"go1.9.4", Compiler:"gc", Platform:"darwin/amd64"}
Unable to connect to the server: EOF

Environment:

I'm connecting from a Darwin host with Kernel version 17.4.0 to an AWS based CoreOS Tectonic Cluster via an empty (no healthy hosts yet) ELB with a TCP Listener.

What happened:

I attempted to talk to the cluster before it was ready and received a bewildering error message:

$ kubectl get all
error: {batch  cronjobs} matches multiple kinds [batch/v1beta1, Kind=CronJob batch/v2alpha1, Kind=CronJob]

Perhaps cluster-info would have been a wiser choice.

What you expected to happen:

Prescriptive error message such as "failed to connect to "

How to reproduce it (as minimally and precisely as possible):

Ask kubectl to talk to an AWS TCP ELB Listener which does not have any healthy hosts.

Anything else we need to know:

$ kubectl --v=100 get all 
I0302 21:29:26.811946    7470 loader.go:357] Config loaded from file /Users/ewdurbin/ernestd/pypi-infra/kubernetes/pypi_2018-03-02_10-21-59/generated/auth/kubeconfig
I0302 21:29:26.813585    7470 round_trippers.go:417] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.9.2 (darwin/amd64) kubernetes/5fa2db2" https://k8s-api.cmh1.psf.io:443/api
I0302 21:29:26.861777    7470 round_trippers.go:436] GET https://k8s-api.cmh1.psf.io:443/api  in 48 milliseconds
I0302 21:29:26.861795    7470 round_trippers.go:442] Response Headers:
I0302 21:29:26.861848    7470 cached_discovery.go:124] skipped caching discovery info due to Get https://k8s-api.cmh1.psf.io:443/api: EOF
I0302 21:29:26.861950    7470 round_trippers.go:417] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.9.2 (darwin/amd64) kubernetes/5fa2db2" https://k8s-api.cmh1.psf.io:443/api
I0302 21:29:26.909375    7470 round_trippers.go:436] GET https://k8s-api.cmh1.psf.io:443/api  in 47 milliseconds
I0302 21:29:26.909402    7470 round_trippers.go:442] Response Headers:
I0302 21:29:26.909428    7470 cached_discovery.go:124] skipped caching discovery info due to Get https://k8s-api.cmh1.psf.io:443/api: EOF
I0302 21:29:26.909741    7470 round_trippers.go:417] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.9.2 (darwin/amd64) kubernetes/5fa2db2" https://k8s-api.cmh1.psf.io:443/api
I0302 21:29:26.956856    7470 round_trippers.go:436] GET https://k8s-api.cmh1.psf.io:443/api  in 47 milliseconds
I0302 21:29:26.956883    7470 round_trippers.go:442] Response Headers:
I0302 21:29:26.956921    7470 cached_discovery.go:124] skipped caching discovery info due to Get https://k8s-api.cmh1.psf.io:443/api: EOF
I0302 21:29:26.956937    7470 factory_object_mapping.go:93] Unable to retrieve API resources, falling back to hardcoded types: Get https://k8s-api.cmh1.psf.io:443/api: EOF
F0302 21:29:26.957292    7470 helpers.go:119] error: {batch  cronjobs} matches multiple kinds [batch/v1beta1, Kind=CronJob batch/v2alpha1, Kind=CronJob]

$ kubectl --v=100 get all 
I0302 21:31:27.344220    9388 loader.go:357] Config loaded from file /Users/ewdurbin/ernestd/pypi-infra/kubernetes/pypi_2018-03-02_10-21-59/generated/auth/kubeconfig
I0302 21:31:27.345723    9388 round_trippers.go:417] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.9.3 (darwin/amd64) kubernetes/d283541" https://k8s-api.cmh1.psf.io:443/api
I0302 21:31:27.393570    9388 round_trippers.go:436] GET https://k8s-api.cmh1.psf.io:443/api  in 47 milliseconds
I0302 21:31:27.393591    9388 round_trippers.go:442] Response Headers:
I0302 21:31:27.393645    9388 cached_discovery.go:124] skipped caching discovery info due to Get https://k8s-api.cmh1.psf.io:443/api: EOF
I0302 21:31:27.393752    9388 round_trippers.go:417] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.9.3 (darwin/amd64) kubernetes/d283541" https://k8s-api.cmh1.psf.io:443/api
I0302 21:31:27.442691    9388 round_trippers.go:436] GET https://k8s-api.cmh1.psf.io:443/api  in 48 milliseconds
I0302 21:31:27.442717    9388 round_trippers.go:442] Response Headers:
I0302 21:31:27.442756    9388 cached_discovery.go:124] skipped caching discovery info due to Get https://k8s-api.cmh1.psf.io:443/api: EOF
I0302 21:31:27.443052    9388 round_trippers.go:417] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.9.3 (darwin/amd64) kubernetes/d283541" https://k8s-api.cmh1.psf.io:443/api
I0302 21:31:27.490758    9388 round_trippers.go:436] GET https://k8s-api.cmh1.psf.io:443/api  in 47 milliseconds
I0302 21:31:27.490775    9388 round_trippers.go:442] Response Headers:
I0302 21:31:27.490835    9388 cached_discovery.go:124] skipped caching discovery info due to Get https://k8s-api.cmh1.psf.io:443/api: EOF
I0302 21:31:27.490850    9388 factory_object_mapping.go:93] Unable to retrieve API resources, falling back to hardcoded types: Get https://k8s-api.cmh1.psf.io:443/api: EOF
F0302 21:31:27.491188    9388 helpers.go:119] error: {batch  cronjobs} matches multiple kinds [batch/v1beta1, Kind=CronJob batch/v2alpha1, Kind=CronJob]

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[nikhita]

/remove-lifecycle rotten

This still looks relevant.

[seans3]

/sig cli
/area kubectl
/priority P3

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.