kubeadm 1.7.2 init blocks on waiting for control plane to be ready #360
Labels
kind/support
Categorizes issue or PR as a support question.
Comments
|
I think this duplicates #353 |
|
Not sure if it duplicates 353 but I'm pretty sure it does not duplicate 308, as you suggested offline. I'm using Docker 1.12.6, which I believe doesn't use cgroupfs by default. |
|
Six days and counting and I still have no answers, just "waiting for control plane to become ready". I have backed down to kubeadm 1.6.1, tried in both Ubuntu and CoreOS and same infuriating result. Anybody, please... I am way outside my area of expertise and just need to get some pods running so I can get back to development. journalctl -r -u kubelet /help-wanted |
|
I have the same problem. Any help would be appreciated. |
|
We released 1.7.3 yesterday. Can you confirm that you're still seeing this issue with kubeadm 1.7.3? |
|
@pipejakob I can confirm that the issue persists on 1.7.3, but when using 1.6.0, this issue does not exists. Except that in 1.6.0 the issue is that kubeadm init get stucked on "First node has registered, but is not ready yet". So... |
|
@christopher-avila Thanks for confirming. So, based on @billmilligan's kubelet logs, it looks like it's failing to connect to the apiserver, which also explains why kubeadm is stuck waiting for the control plane to come up. In order to diagnose what's going wrong, can you look at the Docker logs for kube-apiserver to see what's failing there? It's possible that it's just crashing over and over again with an error message, so you'll probably want to do something like: Then, you can use |
|
I have the same problem, and wait "54286.796454 seconds" for control plane componetes are healthy: |
|
@billmilligan @christopher-avila Would you mind checking this occurs on newer kubeadm versions? If so, can you follow Jakob's comment here and post the output? |
jamiehannaford
added
the
kind/support
|
Closing this for now, probably fixed with v1.8. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/kind bug
What happened:
Never continues from "Created API client, waiting for the control plane to become ready"
What you expected to happen:
Init completes
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
journalctl -u kubelet edited output:
Environment:
Kubernetes version (use
kubectl version):Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.2", GitCommit:"922a86cfcd65915a9b2f69f3f193b8907d741d9c", GitTreeState:"clean", BuildDate:"2017-07-21T08:23:22Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud provider or hardware configuration**:
Metal: HP Proliant DL360 Gp with 48GB memory and 8 cores
VM: Vagrant provisioned 1 CPU, 1 GB memory on VirtualBox, NAT address
OS (e.g. from /etc/os-release):
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1409.7.0
VERSION_ID=1409.7.0
BUILD_ID=2017-07-19-0005
PRETTY_NAME="Container Linux by CoreOS 1409.7.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
Kernel (e.g.
uname -a):4.11.11-coreos kubeadm join on slave node fails preflight checks #1 SMP Tue Jul 18 23:06:59 UTC 2017 x86_64 Intel(R) Xeon(R) CPU E5540 @ 2.53GHz GenuineIntel GNU/Linux
Install tools:
Vagrant
https://github.com/xakraz/kubeadm-installer (recent fork from @luxas https://github.com/luxas/kubeadm-installer)
Others:
/sig area/kubeadm
The text was updated successfully, but these errors were encountered: