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

init error: "kubelet cannot pull or find the following control plane images" #68671

Closed
printfcoder opened this Issue Sep 14, 2018 · 7 comments

Comments

Projects
None yet
3 participants
@printfcoder

printfcoder commented Sep 14, 2018

/sig bug

What happened:

$ kubeadm init

/****

This error is likely caused by:
			- The kubelet is not running
			- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
			- No internet connection is available so the kubelet cannot pull or find the following control plane images:
				- k8s.gcr.io/kube-apiserver-amd64:v1.11.3
				- k8s.gcr.io/kube-controller-manager-amd64:v1.11.3
				- k8s.gcr.io/kube-scheduler-amd64:v1.11.3
				- k8s.gcr.io/etcd-amd64:3.2.18
				- You can check or miligate this in beforehand with "kubeadm config images pull" to make sure the images
				  are downloaded locally and cached.

**My images: **:

root@u-s-1:/tmp# kubeadm config images pull
[config/images] Pulled k8s.gcr.io/kube-apiserver-amd64:v1.11.3
[config/images] Pulled k8s.gcr.io/kube-controller-manager-amd64:v1.11.3
[config/images] Pulled k8s.gcr.io/kube-scheduler-amd64:v1.11.3
[config/images] Pulled k8s.gcr.io/kube-proxy-amd64:v1.11.3
[config/images] Pulled k8s.gcr.io/pause:3.1
[config/images] Pulled k8s.gcr.io/etcd-amd64:3.2.18
[config/images] Pulled k8s.gcr.io/coredns:1.1.3
  • Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T18:02:47Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
root@u-s-1:/tmp# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
  • Kernel (e.g. uname -a):
Linux u-s-1 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
@neolit123

This comment has been minimized.

Show comment
Hide comment
@neolit123

neolit123 Sep 15, 2018

Member

@printfcoder
hi, please try passing --kubernetes-version=1.11.3 to kubeadm init ....

if this doesn't work for you, please re-open the issue.
this is fixed in 1.12.0 which will be released 25th september.

/sig cluster-lifecycle
/close

Member

neolit123 commented Sep 15, 2018

@printfcoder
hi, please try passing --kubernetes-version=1.11.3 to kubeadm init ....

if this doesn't work for you, please re-open the issue.
this is fixed in 1.12.0 which will be released 25th september.

/sig cluster-lifecycle
/close

@k8s-ci-robot

This comment has been minimized.

Show comment
Hide comment
@k8s-ci-robot

k8s-ci-robot Sep 15, 2018

Contributor

@neolit123: Closing this issue.

In response to this:

@printfcoder
hi, please try passing --kubernetes-version=1.11.3 to kubeadm init ....

if this doesn't work for you, please re-open the issue.
this is fixed in 1.12.0 which will be released 25th september.

/sig cluster-lifecycle
/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.

Contributor

k8s-ci-robot commented Sep 15, 2018

@neolit123: Closing this issue.

In response to this:

@printfcoder
hi, please try passing --kubernetes-version=1.11.3 to kubeadm init ....

if this doesn't work for you, please re-open the issue.
this is fixed in 1.12.0 which will be released 25th september.

/sig cluster-lifecycle
/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.

@printfcoder

This comment has been minimized.

Show comment
Hide comment
@printfcoder

printfcoder Sep 15, 2018

@neolit123
Thks for your replication.
Certainly the kb version I used was 1.11.3. Now, I pass the version --kubernetes-version=1.11.3 explicitly.

root@u-s-1:~# kubeadm init --kubernetes-version=1.11.3
[init] using Kubernetes version: v1.11.3
....
[init] this might take a minute or longer if the control plane images have to be pulled
....
		Unfortunately, an error has occurred:
			timed out waiting for the condition

		This error is likely caused by:
			- The kubelet is not running
			- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
			- No internet connection is available so the kubelet cannot pull or find the following control plane images:
				- k8s.gcr.io/kube-apiserver-amd64:v1.11.3
				- k8s.gcr.io/kube-controller-manager-amd64:v1.11.3
				- k8s.gcr.io/kube-scheduler-amd64:v1.11.3
				- k8s.gcr.io/etcd-amd64:3.2.18
				- You can check or miligate this in beforehand with "kubeadm config images pull" to make sure the images
				  are downloaded locally and cached.
...

So, the error is still here.
/sig cluster-lifecycle
/reopen

printfcoder commented Sep 15, 2018

@neolit123
Thks for your replication.
Certainly the kb version I used was 1.11.3. Now, I pass the version --kubernetes-version=1.11.3 explicitly.

root@u-s-1:~# kubeadm init --kubernetes-version=1.11.3
[init] using Kubernetes version: v1.11.3
....
[init] this might take a minute or longer if the control plane images have to be pulled
....
		Unfortunately, an error has occurred:
			timed out waiting for the condition

		This error is likely caused by:
			- The kubelet is not running
			- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
			- No internet connection is available so the kubelet cannot pull or find the following control plane images:
				- k8s.gcr.io/kube-apiserver-amd64:v1.11.3
				- k8s.gcr.io/kube-controller-manager-amd64:v1.11.3
				- k8s.gcr.io/kube-scheduler-amd64:v1.11.3
				- k8s.gcr.io/etcd-amd64:3.2.18
				- You can check or miligate this in beforehand with "kubeadm config images pull" to make sure the images
				  are downloaded locally and cached.
...

So, the error is still here.
/sig cluster-lifecycle
/reopen

@neolit123

This comment has been minimized.

Show comment
Hide comment
@neolit123

neolit123 Sep 15, 2018

Member

@printfcoder
can your try pre-pulling the images:
kubeadm config images list --kubernetes-version=1.11.3
kubeadm config images pull --kubernetes-version=1.11.3

but it could be a different error.

Member

neolit123 commented Sep 15, 2018

@printfcoder
can your try pre-pulling the images:
kubeadm config images list --kubernetes-version=1.11.3
kubeadm config images pull --kubernetes-version=1.11.3

but it could be a different error.

@printfcoder

This comment has been minimized.

Show comment
Hide comment
@printfcoder

printfcoder Sep 16, 2018

@neolit123

root@u-s-1:~# kubeadm config images list --kubernetes-version=1.11.3
k8s.gcr.io/kube-apiserver-amd64:v1.11.3
k8s.gcr.io/kube-controller-manager-amd64:v1.11.3
k8s.gcr.io/kube-scheduler-amd64:v1.11.3
k8s.gcr.io/kube-proxy-amd64:v1.11.3
k8s.gcr.io/pause:3.1
k8s.gcr.io/etcd-amd64:3.2.18
k8s.gcr.io/coredns:1.1.3

root@u-s-1:~# kubeadm config images pull --kubernetes-version=1.11.3
failed to pull image "k8s.gcr.io/kube-apiserver-amd64:v1.11.3": exit status 1

printfcoder commented Sep 16, 2018

@neolit123

root@u-s-1:~# kubeadm config images list --kubernetes-version=1.11.3
k8s.gcr.io/kube-apiserver-amd64:v1.11.3
k8s.gcr.io/kube-controller-manager-amd64:v1.11.3
k8s.gcr.io/kube-scheduler-amd64:v1.11.3
k8s.gcr.io/kube-proxy-amd64:v1.11.3
k8s.gcr.io/pause:3.1
k8s.gcr.io/etcd-amd64:3.2.18
k8s.gcr.io/coredns:1.1.3

root@u-s-1:~# kubeadm config images pull --kubernetes-version=1.11.3
failed to pull image "k8s.gcr.io/kube-apiserver-amd64:v1.11.3": exit status 1
@neolit123

This comment has been minimized.

Show comment
Hide comment
@neolit123

neolit123 Sep 17, 2018

Member

@printfcoder
we have better errors reports in 1.12, but my guess here is that you don't have internet connectivity to k8s.gcr.io.

does this work:
docker pull k8s.gcr.io/kube-apiserver-amd64:v1.11.3
?

Member

neolit123 commented Sep 17, 2018

@printfcoder
we have better errors reports in 1.12, but my guess here is that you don't have internet connectivity to k8s.gcr.io.

does this work:
docker pull k8s.gcr.io/kube-apiserver-amd64:v1.11.3
?

@printfcoder

This comment has been minimized.

Show comment
Hide comment
@printfcoder

printfcoder Sep 18, 2018

@neolit123
Yes,it works via a proxy server.

I have tried both docker pull k8s.gcr.io/** and kubeadm config images list, and the images pulled fine. When cmd docker pull pulled OK then I removed all the images then tried kubeadm config images list, both of them two method to get images work very good although very slow.

printfcoder commented Sep 18, 2018

@neolit123
Yes,it works via a proxy server.

I have tried both docker pull k8s.gcr.io/** and kubeadm config images list, and the images pulled fine. When cmd docker pull pulled OK then I removed all the images then tried kubeadm config images list, both of them two method to get images work very good although very slow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment