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:21
Elapsed3m23s
Revision3d427ccafaa292338e81d8889d9f20be294c4610
Refs 2371

No Test Failures!


Error lines from build-log.txt

... skipping 123 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
discovery:
  bootstrapToken:
    apiServerEndpoint: 172.17.0.5:6443
    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.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
controlPlane:
  localAPIEndpoint:
    advertiseAddress: 172.17.0.5
... 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.5
---
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.5: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.5: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:22:17.647759     214 checks.go:372] validating the presence of executable ebtables
I1007 20:22:17.647806     214 checks.go:372] validating the presence of executable ethtool
I1007 20:22:17.647829     214 checks.go:372] validating the presence of executable socat
I1007 20:22:17.647880     214 checks.go:372] validating the presence of executable tc
I1007 20:22:17.647898     214 checks.go:372] validating the presence of executable touch
I1007 20:22:17.647926     214 checks.go:520] 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:22:17.652486     214 checks.go:403] 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 162 lines ...
I1007 20:23:00.125064     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:00.624057     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:01.124123     214 round_trippers.go:454] GET https://172.17.0.5: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.
I1007 20:23:01.624066     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
[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:23:02.125218     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:02.624422     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:03.124319     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:03.624357     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:04.124332     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:04.625041     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:05.125109     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:05.624969     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:06.125149     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:06.624443     214 round_trippers.go:454] GET https://172.17.0.5: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:23:07.124170     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:07.624233     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:08.124265     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:08.624332     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:09.124203     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:09.624241     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 20:23:14.624067     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:15.125200     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:15.625224     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:16.124085     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:16.625011     214 round_trippers.go:454] GET https://172.17.0.5: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:23:17.124444     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:17.624716     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:18.124572     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:18.624637     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:19.124729     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:19.624461     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 20:23:34.624624     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:35.124677     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:35.624952     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:36.125191     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:36.625289     214 round_trippers.go:454] GET https://172.17.0.5: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:23:37.124749     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:37.624968     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:38.124891     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:38.624826     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:39.124655     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:39.624539     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 20:24:14.624785     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:15.124851     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:15.624839     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:16.124849     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:16.624874     214 round_trippers.go:454] GET https://172.17.0.5: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:22:17.589313     214 initconfiguration.go:247] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
I1007 20:22:17.595722     214 kubelet.go:203] the value of KubeletConfiguration.cgroupDriver is empty; setting it to "systemd"
[init] Using Kubernetes version: v1.22.1
... skipping 23 lines ...
I1007 20:22:17.647759     214 checks.go:372] validating the presence of executable ebtables
I1007 20:22:17.647806     214 checks.go:372] validating the presence of executable ethtool
I1007 20:22:17.647829     214 checks.go:372] validating the presence of executable socat
I1007 20:22:17.647880     214 checks.go:372] validating the presence of executable tc
I1007 20:22:17.647898     214 checks.go:372] validating the presence of executable touch
I1007 20:22:17.647926     214 checks.go:520] 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:22:17.652486     214 checks.go:403] 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 162 lines ...
I1007 20:23:00.125064     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:00.624057     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:01.124123     214 round_trippers.go:454] GET https://172.17.0.5: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.
I1007 20:23:01.624066     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
[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:23:02.125218     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:02.624422     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:03.124319     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:03.624357     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:04.124332     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:04.625041     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:05.125109     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:05.624969     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:06.125149     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:06.624443     214 round_trippers.go:454] GET https://172.17.0.5: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:23:07.124170     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:07.624233     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:08.124265     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:08.624332     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:09.124203     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:09.624241     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 20:23:14.624067     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:15.125200     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:15.625224     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:16.124085     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:16.625011     214 round_trippers.go:454] GET https://172.17.0.5: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:23:17.124444     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:17.624716     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:18.124572     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:18.624637     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:19.124729     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:19.624461     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 20:23:34.624624     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:35.124677     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:35.624952     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:36.125191     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:36.625289     214 round_trippers.go:454] GET https://172.17.0.5: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:23:37.124749     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:37.624968     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:38.124891     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:38.624826     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:39.124655     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:39.624539     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 20:24:14.624785     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:15.124851     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:15.624839     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:16.124849     214 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:16.624874     214 round_trippers.go:454] GET https://172.17.0.5: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 ...