-
Notifications
You must be signed in to change notification settings - Fork 43.2k
kubeadm 1.8.0 init fails with "/var/lib/kubelet is not empty" #53356
Copy link
Copy link
Closed
Labels
area/kubeadmkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.milestone/needs-approvalpriority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.Highest priority. Must be actively worked on as someone's top priority right now.sig/cluster-lifecycleCategorizes an issue or PR as relevant to SIG Cluster Lifecycle.Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Milestone
Metadata
Metadata
Assignees
Labels
area/kubeadmkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.milestone/needs-approvalpriority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.Highest priority. Must be actively worked on as someone's top priority right now.sig/cluster-lifecycleCategorizes an issue or PR as relevant to SIG Cluster Lifecycle.Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
On a fresh Ubuntu 16.04.3 system booted from the official cloud image,
kubeadm initfails because/var/lib/kubeletexists.What you expected to happen:
kubeadm successfully initializes the cluster
How to reproduce it (as minimally and precisely as possible):
apt-get install -y apt-transport-https docker.iokubeadm initAnything else we need to know?:
Contents of
/var/lib/kubelet:Environment:
kubectl version):uname -a):Linux kubemaster 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux