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.

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

kubeadm blocks waiting for 'waiting for the control plane to become ready' #35684

Closed
jiaqizho opened this issue Oct 27, 2016 · 5 comments
Closed

Comments

@jiaqizho
Copy link

i saw the issue #33544 and all the issue about this question. but it not work ! i have no method to hand it .

Environment:


kubernetes-dashboard-amd64:v1.4.0

[root@hostname kubernetes-dashboard]# kubectl version
Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.1", GitCommit:"33cf7b9acbb2cb7c9c72a10d6636321fb180b159", GitTreeState:"clean", BuildDate:"2016-10-10T18:19:49Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.1", GitCommit:"33cf7b9acbb2cb7c9c72a10d6636321fb180b159", GitTreeState:"clean", BuildDate:"2016-10-10T18:13:36Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Operating system: CentOS 7

when i cmd :
kubeadm init

then it output:

[root@hostname calico]# kubeadm init
Running pre-flight checks
<master/tokens> generated token: "c0fe76.eca2db20ad994059"
<master/pki> generated Certificate Authority key and certificate:
Issuer: CN=kubernetes | Subject: CN=kubernetes | CA: true
Not before: 2016-10-27 07:25:30 +0000 UTC Not After: 2026-10-25 07:25:30 +0000 UTC
Public: /etc/kubernetes/pki/ca-pub.pem
Private: /etc/kubernetes/pki/ca-key.pem
Cert: /etc/kubernetes/pki/ca.pem
<master/pki> generated API Server key and certificate:
Issuer: CN=kubernetes | Subject: CN=kube-apiserver | CA: false
Not before: 2016-10-27 07:25:30 +0000 UTC Not After: 2017-10-27 07:25:31 +0000 UTC
Alternate Names: [10.0.2.15 10.0.0.1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local]
Public: /etc/kubernetes/pki/apiserver-pub.pem
Private: /etc/kubernetes/pki/apiserver-key.pem
Cert: /etc/kubernetes/pki/apiserver.pem
<master/pki> generated Service Account Signing keys:
Public: /etc/kubernetes/pki/sa-pub.pem
Private: /etc/kubernetes/pki/sa-key.pem
<master/pki> created keys and certificates in "/etc/kubernetes/pki"
<util/kubeconfig> created "/etc/kubernetes/kubelet.conf"
<util/kubeconfig> created "/etc/kubernetes/admin.conf"
<master/apiclient> created API client configuration
<master/apiclient> created API client, waiting for the control plane to become ready


it blocked at waiting for the control plane to become ready.

then i get the pods

[root@hostname kubernetes-dashboard]# kubectl get pods --namespace=kube-system
NAME                                    READY     STATUS              RESTARTS   AGE
etcd-hostname                           1/1       Running             6          1h
kube-apiserver-hostname                 1/1       Running             2          1h
kube-controller-manager-hostname        1/1       Running             1          1h
kube-scheduler-hostname                 1/1       Running             1          1h
kubernetes-dashboard-1655269645-pyxlv   0/1       ContainerCreating   0          44m
weave-net-8kxdo                         2/2       Running             14         45m

the wave is i created after cmd kubeadm

i have already closed the selinux . and set the proxy in shell(/etc/profile) and docker(systemd).

what fuck going on ???

@jiaqizho
Copy link
Author

or is k8s not support at virtualbox machine ?
i got lots of question at virtualbox , i have build k8s at coreos on virtualbox , it comes lots of problem too.

@brightzheng100
Copy link

Same issue in my Ubuntu 16 64bit.

bright@ubuntu16:~$ sudo docker version
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64
bright@ubuntu16:~$ kubeadm version
kubeadm version: version.Info{Major:"1", Minor:"5+", GitVersion:"v1.5.0-alpha.0.1534+cf7301f16c0363-dirty", GitCommit:"cf7301f16c036363c4fdcb5d4d0c867720214598", GitTreeState:"dirty", BuildDate:"2016-09-27T18:10:39Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

While issuing kubeadm init, it would be hung at "waiting for the control plane to become ready":

bright@ubuntu16:~$ sudo kubeadm init
<master/tokens> generated token: "efd816.3d733107e08dccd0"
<master/pki> created keys and certificates in "/etc/kubernetes/pki"
<util/kubeconfig> created "/etc/kubernetes/admin.conf"
<util/kubeconfig> created "/etc/kubernetes/kubelet.conf"
<master/apiclient> created API client configuration
<master/apiclient> created API client, waiting for the control plane to become ready

@yamnicz3k
Copy link

yamnicz3k commented Oct 28, 2016

I had similar problem.

# kubeadm version
kubeadm version: version.Info{Major:"1", Minor:"5+", GitVersion:"v1.5.0-alpha.0.1534+cf7301f16c0363-dirty", GitCommit:"cf7301f16c036363c4fdcb5d4d0c867720214598", GitTreeState:"dirty", BuildDate:"2016-09-27T18:10:39Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

# docker version
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        
 OS/Arch:      linux/amd64

My infrastructure is behind proxy, so i had to add proxy conf to my docker systemd service and restart it.

Kubernetes cluster on docker 1.12.3 works fine now.

@jiaqizho
Copy link
Author

i find that maybe the k8s version 1.4 is not work.
then i change it to 1.4.1 and it worked .

@luxas
Copy link
Member

luxas commented May 30, 2017

If this issue exists with kubeadm v1.6 as well, please reopen an issue in the https://github.com/kubernetes/kubeadm/issues repo

@luxas luxas closed this as completed May 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants