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.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.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.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 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
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 35 lines ...
I1007 20:22:16.367066     213 checks.go:377] validating the presence of executable ebtables
I1007 20:22:16.367105     213 checks.go:377] validating the presence of executable ethtool
I1007 20:22:16.367127     213 checks.go:377] validating the presence of executable socat
I1007 20:22:16.367160     213 checks.go:377] validating the presence of executable tc
I1007 20:22:16.367230     213 checks.go:377] validating the presence of executable touch
I1007 20:22:16.367352     213 checks.go:525] running all checks
[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
CGROUPS_FREEZER: enabled
CGROUPS_MEMORY: enabled
CGROUPS_PIDS: enabled
CGROUPS_HUGETLB: enabled
	[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:16.372083     213 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
I1007 20:22:16.372545     213 checks.go:623] validating kubelet version
I1007 20:22:16.442022     213 checks.go:129] validating if the "kubelet" service is enabled and active
I1007 20:22:16.453636     213 checks.go:202] validating availability of port 10250
I1007 20:22:16.453853     213 checks.go:202] validating availability of port 2379
I1007 20:22:16.454036     213 checks.go:202] validating availability of port 2380
... skipping 152 lines ...
I1007 20:23:00.074445     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:00.574320     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:01.073859     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] Initial timeout of 40s passed.
I1007 20:23:01.573410     213 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:02.073674     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:02.573466     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:03.073631     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:03.573622     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:04.073455     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:04.574347     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:05.074335     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:05.574262     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:06.074102     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:06.574537     213 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.074537     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:07.574543     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:08.074482     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:08.574553     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:09.074060     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:09.573996     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 20:23:14.574631     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:15.074616     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:15.573413     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:16.074463     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:16.573625     213 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.073565     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:17.573564     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:18.073546     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:18.573524     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:19.073581     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:19.574620     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 20:23:34.574491     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:35.074383     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:35.574385     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:36.074260     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:36.574470     213 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.074259     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:37.574454     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:38.074490     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:38.574558     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:39.074607     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:39.573436     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 20:24:14.574042     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:15.073996     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:15.573817     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:16.073815     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:16.574119     213 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:16.318360     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:22:16.330836     213 kubelet.go:259] setting the KubeletConfiguration cgroupDriver to "systemd"
[init] Using Kubernetes version: v1.21.2
... skipping 23 lines ...
I1007 20:22:16.367066     213 checks.go:377] validating the presence of executable ebtables
I1007 20:22:16.367105     213 checks.go:377] validating the presence of executable ethtool
I1007 20:22:16.367127     213 checks.go:377] validating the presence of executable socat
I1007 20:22:16.367160     213 checks.go:377] validating the presence of executable tc
I1007 20:22:16.367230     213 checks.go:377] validating the presence of executable touch
I1007 20:22:16.367352     213 checks.go:525] running all checks
[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
CGROUPS_FREEZER: enabled
CGROUPS_MEMORY: enabled
CGROUPS_PIDS: enabled
CGROUPS_HUGETLB: enabled
	[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:16.372083     213 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
I1007 20:22:16.372545     213 checks.go:623] validating kubelet version
I1007 20:22:16.442022     213 checks.go:129] validating if the "kubelet" service is enabled and active
I1007 20:22:16.453636     213 checks.go:202] validating availability of port 10250
I1007 20:22:16.453853     213 checks.go:202] validating availability of port 2379
I1007 20:22:16.454036     213 checks.go:202] validating availability of port 2380
... skipping 152 lines ...
I1007 20:23:00.074445     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:00.574320     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:01.073859     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] Initial timeout of 40s passed.
I1007 20:23:01.573410     213 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:02.073674     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:02.573466     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:03.073631     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:03.573622     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:04.073455     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:04.574347     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:05.074335     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:05.574262     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:06.074102     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:06.574537     213 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.074537     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:07.574543     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:08.074482     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:08.574553     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:09.074060     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:09.573996     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 20:23:14.574631     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:15.074616     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:15.573413     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:16.074463     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:16.573625     213 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.073565     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:17.573564     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:18.073546     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:18.573524     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:19.073581     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:19.574620     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 20:23:34.574491     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:35.074383     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:35.574385     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:36.074260     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:36.574470     213 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.074259     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:37.574454     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:38.074490     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:38.574558     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:39.074607     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:23:39.573436     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 20:24:14.574042     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:15.073996     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:15.573817     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:16.073815     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1007 20:24:16.574119     213 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 ...