Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cluster/kube-up.sh loop forever in version 1.3.0 in AWS #28593

Closed
talk2vino opened this issue Jul 7, 2016 · 2 comments
Closed

cluster/kube-up.sh loop forever in version 1.3.0 in AWS #28593

talk2vino opened this issue Jul 7, 2016 · 2 comments

Comments

@talk2vino
Copy link
Contributor

talk2vino commented Jul 7, 2016 •
edited
Loading

Environment: Kubernetes in AWS

Previously i tried 30+ times in version Kubernetes 1.2.4 on AWS . It works flawless all the times.

Today when i tried the same with fresh new cluster with kubernetes version 1.3.0 . The cluster initialisation loops forever for 30 minutes

Creating autoscaling group
 0 minions started; waiting
 0 minions started; waiting
 0 minions started; waiting
 0 minions started; waiting
 5 minions started; ready
Waiting for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This might loop forever if there was some uncaught error during start
  up.

.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

kube version

kubectl version
Client Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.0", GitCommit:"283137936a498aed572ee22af6774b6fb6e9fd94", GitTreeState:"clean", BuildDate:"2016-07-01T19:26:38Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}

I go and checked each of the nodes with "docker ps" , and all of the nodes responded.

The below are the kube-apiserver logs from Master.

tail -f /var/log/kube-apiserver.log
I0707 10:46:01.682375       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-57.us-west-2.compute.internal/status: (3.478826ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.57:39608]
I0707 10:46:03.321912       7 logs.go:41] http: TLS handshake error from 182.74.106.3:37435: tls: client offered an unsupported, maximum protocol version of 301
I0707 10:46:03.684879       7 handlers.go:165] GET /api/v1/nodes: (2.205527ms) 200 [[pod_nanny/v0.0.0 (linux/amd64) kubernetes/$Format] 172.20.0.57:56892]
I0707 10:46:03.688692       7 handlers.go:165] GET /api/v1/namespaces/kube-system/pods/heapster-v1.1.0-3166934156-x3pqp: (1.511805ms) 200 [[pod_nanny/v0.0.0 (linux/amd64) kubernetes/$Format] 172.20.0.57:56892]
I0707 10:46:03.719907       7 handlers.go:165] GET /api/v1/nodes: (1.735749ms) 200 [[pod_nanny/v0.0.0 (linux/amd64) kubernetes/$Format] 172.20.0.57:56894]
I0707 10:46:03.723690       7 handlers.go:165] GET /api/v1/namespaces/kube-system/pods/heapster-v1.1.0-3166934156-x3pqp: (1.531456ms) 200 [[pod_nanny/v0.0.0 (linux/amd64) kubernetes/$Format] 172.20.0.57:56894]
I0707 10:46:04.832582       7 handlers.go:165] GET /healthz: (98.701µs) 200 [[Go-http-client/1.1] 127.0.0.1:55365]
I0707 10:46:05.082949       7 handlers.go:165] GET /api/v1/nodes: (1.584727ms) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/node-controller] 127.0.0.1:55358]
I0707 10:46:05.244386       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-58.us-west-2.compute.internal: (1.078198ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.58:34755]
I0707 10:46:05.252279       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-58.us-west-2.compute.internal/status: (3.069901ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.58:34755]
I0707 10:46:05.962474       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-54.us-west-2.compute.internal: (1.352055ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.54:55878]
I0707 10:46:05.968562       7 logs.go:41] http: TLS handshake error from 182.74.106.3:37436: tls: client offered an unsupported, maximum protocol version of 301
I0707 10:46:05.971862       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-54.us-west-2.compute.internal/status: (3.127346ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.54:55878]
I0707 10:46:07.210960       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-56.us-west-2.compute.internal: (1.406006ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.56:57991]
I0707 10:46:07.221951       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-56.us-west-2.compute.internal/status: (3.563008ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.56:57991]
I0707 10:46:08.619418       7 logs.go:41] http: TLS handshake error from 182.74.106.3:37437: tls: client offered an unsupported, maximum protocol version of 301
I0707 10:46:08.640468       7 handlers.go:165] GET /api/v1/watch/secrets?fieldSelector=type%3Dkubernetes.io%2Fservice-account-token&resourceVersion=15&timeoutSeconds=573: (9m33.000413463s) 200 [[kube-apiserver/v1.3.0 (linux/amd64) kubernetes/2831379] 127.0.0.1:51381]
I0707 10:46:09.977067       7 handlers.go:165] GET /api/v1/nodes: (1.621331ms) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.978726       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-54.us-west-2.compute.internal: (917.251µs) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.980799       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-54.us-west-2.compute.internal/status: (1.555254ms) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.982049       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-55.us-west-2.compute.internal: (811.358µs) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.983941       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-55.us-west-2.compute.internal/status: (1.375196ms) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.985281       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-56.us-west-2.compute.internal: (894.413µs) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.987236       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-56.us-west-2.compute.internal/status: (1.474856ms) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.988493       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-57.us-west-2.compute.internal: (856.196µs) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.990389       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-57.us-west-2.compute.internal/status: (1.414768ms) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.991670       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-58.us-west-2.compute.internal: (851.331µs) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:09.993575       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-58.us-west-2.compute.internal/status: (1.359682ms) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/route-controller] 127.0.0.1:55358]
I0707 10:46:10.085520       7 handlers.go:165] GET /api/v1/nodes: (1.539579ms) 200 [[kube-controller-manager/v1.3.0 (linux/amd64) kubernetes/2831379/node-controller] 127.0.0.1:55358]
I0707 10:46:10.648457       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-55.us-west-2.compute.internal: (1.396064ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.55:47727]
I0707 10:46:10.658403       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-55.us-west-2.compute.internal/status: (5.005459ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.55:47727]
I0707 10:46:11.271671       7 logs.go:41] http: TLS handshake error from 182.74.106.3:37438: tls: client offered an unsupported, maximum protocol version of 301
I0707 10:46:11.684834       7 handlers.go:165] GET /api/v1/nodes/ip-172-20-0-57.us-west-2.compute.internal: (1.328298ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.57:39608]
I0707 10:46:11.693274       7 handlers.go:165] PUT /api/v1/nodes/ip-172-20-0-57.us-west-2.compute.internal/status: (2.990194ms) 200 [[kubelet/v1.3.0 (linux/amd64) kubernetes/2831379] 172.20.0.57:39608]
@talk2vino talk2vino changed the title cluster/kube-up.sh loop forever in version 1.3.0 cluster/kube-up.sh loop forever in version 1.3.0 in AWS Jul 9, 2016
@chandanpal
Copy link

chandanpal commented Feb 28, 2017 •
edited
Loading

How did you fix this issue??

@talk2vino
Copy link
Contributor Author

@chandanpal

The issue is more related to the curl version you have in the host that u are trying to run the kubernetes.

#28888. Add the tlsv1.2 in AWS utils.sh script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chandanpal @talk2vino