kubeadm init failed when inside a cloud-init script on openstack

Created on 2 Mar 2019  路  2Comments  路  Source: kubernetes/kubeadm

What keywords did you search in kubeadm issues before filing this one?

kubeadm init failed control-plan cloud-init
If you have found any duplicates, you should instead reply there and close this page.

If you have not found any duplicates, delete this section and continue on.

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

kubeadm version (use kubeadm version):
latest
Environment:

  • Kubernetes version (use kubectl version):
    1.13
  • Cloud provider or hardware configuration:
    openstack spike
  • OS (e.g. from /etc/os-release):
    debian 9
  • Kernel (e.g. uname -a):
  • Others:
    docker 1.18

What happened?

after install docker and k8s in my cloud init script on my master vm, i launch kubeadm init and the control plane failed. If i stop the script juste before kubeadm and then logged to the vm and launch kubeadm init with sudo it s work. why the cloud init script is different ?
i launch kubeadm init --pod-network-cidr=10.244.0.0/16
here is the failed
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s

What you expected to happen?

kubeadm init --pod-network-cidr=10.244.0.0/16 on the vm

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

[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 22.504496 seconds
[uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system 禄 Namespace

Anything else we need to know?

i am behind a corporate proxy wel confugured on curl, apt and docker

areprovideopenstack help wanted

All 2 comments

Can you try to unset proxy when you run kubeadm init? Because i remember that i used to set proxy the init failed.

you made my day, i don t know why but after unset proxys, it works here is the log
thx
Bruno
[[0;32m OK [0m] Stopped kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Stopped kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Stopped kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Stopped kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Stopped kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Stopped kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Stopped kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Stopped kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started kubelet: The Kubernetes Node Agent.
[[0;32m OK [0m] Started Kubernetes systemd probe.

Was this page helpful?
0 / 5 - 0 ratings