This job view page is being replaced by Spyglass soon. Check out the new job view.
PRhickeyma: 🌱 Upgrade e2e test for latest Kubernetes versions
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-07 20:35
Elapsed3m48s
Revisionea0cd76fea8395c85a7d9e56c172dd1c47f2ec9c
Refs 2371

No Test Failures!


Error lines from build-log.txt

... skipping 122 lines ...
localAPIEndpoint:
  advertiseAddress: 172.17.0.5
  bindPort: 6443
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    fail-swap-on: "false"
    node-ip: 172.17.0.5
---
apiVersion: kubeadm.k8s.io/v1beta2
discovery:
  bootstrapToken:
    apiServerEndpoint: 172.17.0.3:6443
    token: abcdef.0123456789abcdef
    unsafeSkipCAVerification: true
kind: JoinConfiguration
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    fail-swap-on: "false"
    node-ip: 172.17.0.5
---
apiVersion: kubelet.config.k8s.io/v1beta1
evictionHard:
  imagefs.available: 0%
  nodefs.available: 0%
... skipping 29 lines ...
localAPIEndpoint:
  advertiseAddress: 172.17.0.3
  bindPort: 6443
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    fail-swap-on: "false"
    node-ip: 172.17.0.3
---
apiVersion: kubeadm.k8s.io/v1beta2
controlPlane:
  localAPIEndpoint:
    advertiseAddress: 172.17.0.3
... skipping 4 lines ...
    token: abcdef.0123456789abcdef
    unsafeSkipCAVerification: true
kind: JoinConfiguration
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    fail-swap-on: "false"
    node-ip: 172.17.0.3
---
apiVersion: kubelet.config.k8s.io/v1beta1
evictionHard:
  imagefs.available: 0%
  nodefs.available: 0%
... skipping 29 lines ...
localAPIEndpoint:
  advertiseAddress: 172.17.0.4
  bindPort: 6443
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    fail-swap-on: "false"
    node-ip: 172.17.0.4
---
apiVersion: kubeadm.k8s.io/v1beta2
discovery:
  bootstrapToken:
    apiServerEndpoint: 172.17.0.3:6443
    token: abcdef.0123456789abcdef
    unsafeSkipCAVerification: true
kind: JoinConfiguration
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    fail-swap-on: "false"
    node-ip: 172.17.0.4
---
apiVersion: kubelet.config.k8s.io/v1beta1
evictionHard:
  imagefs.available: 0%
  nodefs.available: 0%
... skipping 29 lines ...
localAPIEndpoint:
  advertiseAddress: 172.17.0.2
  bindPort: 6443
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    fail-swap-on: "false"
    node-ip: 172.17.0.2
---
apiVersion: kubeadm.k8s.io/v1beta2
discovery:
  bootstrapToken:
    apiServerEndpoint: 172.17.0.3:6443
    token: abcdef.0123456789abcdef
    unsafeSkipCAVerification: true
kind: JoinConfiguration
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    fail-swap-on: "false"
    node-ip: 172.17.0.2
---
apiVersion: kubelet.config.k8s.io/v1beta1
evictionHard:
  imagefs.available: 0%
  nodefs.available: 0%
... skipping 35 lines ...
I1007 20:36:49.565107     213 checks.go:377] validating the presence of executable ebtables
I1007 20:36:49.565254     213 checks.go:377] validating the presence of executable ethtool
I1007 20:36:49.565321     213 checks.go:377] validating the presence of executable socat
I1007 20:36:49.565406     213 checks.go:377] validating the presence of executable tc
I1007 20:36:49.565485     213 checks.go:377] validating the presence of executable touch
I1007 20:36:49.565526     213 checks.go:525] running all checks
	[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1046-gke\n", err: exit status 1
I1007 20:36:49.580124     213 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1046-gke
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
... skipping 160 lines ...
I1007 20:37:35.682197     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:36.182111     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:36.681823     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:37.181561     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I1007 20:37:37.681312     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:38.182424     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:38.681572     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:39.181605     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:39.681640     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:40.181508     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:40.681532     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:41.181678     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:41.681526     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:42.181372     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:42.681386     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I1007 20:37:43.183141     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:43.681562     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:44.181507     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:44.681599     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:45.181472     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:45.681612     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 20:37:50.681497     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:51.181459     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:51.681493     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:52.181481     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:52.681469     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I1007 20:37:53.182094     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:53.682302     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:54.181432     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:54.681530     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:55.181445     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:55.681496     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 20:38:10.681499     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:11.181342     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:11.681199     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:12.182151     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:12.681357     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I1007 20:38:13.182205     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:13.682293     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:14.182307     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:14.681478     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:15.181320     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:15.682215     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 20:38:50.681400     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:51.181385     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:51.681405     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:52.181314     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:52.682194     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.

	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)

	If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
		- 'systemctl status kubelet'
		- 'journalctl -xeu kubelet'

	Additionally, a control plane component may have crashed or exited when started by the container runtime.
	To troubleshoot, list all containers using your preferred container runtimes CLI.

... skipping 24 lines ...
main.main
	_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
	/usr/local/go/src/runtime/proc.go:225
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1371
error execution phase wait-control-plane
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:235
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
... skipping 11 lines ...
	_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
	/usr/local/go/src/runtime/proc.go:225
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1371
 ✗ Starting control-plane 🕹ī¸
ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged kind-control-plane kubeadm init --ignore-preflight-errors=all --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1

Output:
I1007 20:36:49.472235     213 initconfiguration.go:246] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
I1007 20:36:49.489888     213 kubelet.go:259] setting the KubeletConfiguration cgroupDriver to "systemd"
[init] Using Kubernetes version: v1.21.2
... skipping 23 lines ...
I1007 20:36:49.565107     213 checks.go:377] validating the presence of executable ebtables
I1007 20:36:49.565254     213 checks.go:377] validating the presence of executable ethtool
I1007 20:36:49.565321     213 checks.go:377] validating the presence of executable socat
I1007 20:36:49.565406     213 checks.go:377] validating the presence of executable tc
I1007 20:36:49.565485     213 checks.go:377] validating the presence of executable touch
I1007 20:36:49.565526     213 checks.go:525] running all checks
	[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1046-gke\n", err: exit status 1
I1007 20:36:49.580124     213 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1046-gke
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
... skipping 160 lines ...
I1007 20:37:35.682197     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:36.182111     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:36.681823     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:37.181561     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I1007 20:37:37.681312     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:38.182424     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:38.681572     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:39.181605     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:39.681640     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:40.181508     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:40.681532     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:41.181678     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:41.681526     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:42.181372     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:42.681386     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I1007 20:37:43.183141     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:43.681562     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:44.181507     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:44.681599     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:45.181472     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:45.681612     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 20:37:50.681497     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:51.181459     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:51.681493     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:52.181481     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:52.681469     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I1007 20:37:53.182094     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:53.682302     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:54.181432     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:54.681530     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:55.181445     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:37:55.681496     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 20:38:10.681499     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:11.181342     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:11.681199     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:12.182151     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:12.681357     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
I1007 20:38:13.182205     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:13.682293     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:14.182307     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:14.681478     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:15.181320     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:15.682215     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 20:38:50.681400     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:51.181385     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:51.681405     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:52.181314     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:38:52.682194     213 round_trippers.go:454] GET https://172.17.0.3:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.

	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)

	If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
		- 'systemctl status kubelet'
		- 'journalctl -xeu kubelet'

	Additionally, a control plane component may have crashed or exited when started by the container runtime.
	To troubleshoot, list all containers using your preferred container runtimes CLI.

... skipping 24 lines ...
main.main
	_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
	/usr/local/go/src/runtime/proc.go:225
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1371
error execution phase wait-control-plane
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:235
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
... skipping 65 lines ...