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 23:18
Elapsed3m20s
Revisionea0cd76fea8395c85a7d9e56c172dd1c47f2ec9c
Refs 2371

No Test Failures!


Error lines from build-log.txt

... skipping 123 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.2: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.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
controlPlane:
  localAPIEndpoint:
    advertiseAddress: 172.17.0.2
... 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.2
---
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.2: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.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.2: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 23:19:41.727826     213 checks.go:372] validating the presence of executable ebtables
I1007 23:19:41.727864     213 checks.go:372] validating the presence of executable ethtool
I1007 23:19:41.727885     213 checks.go:372] validating the presence of executable socat
I1007 23:19:41.727928     213 checks.go:372] validating the presence of executable tc
I1007 23:19:41.727996     213 checks.go:372] validating the presence of executable touch
I1007 23:19:41.728046     213 checks.go:520] 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 23:19:41.732714     213 checks.go:403] checking whether the given node name is valid and reachable using net.LookupHost
I1007 23:19:41.732976     213 checks.go:618] validating kubelet version
I1007 23:19:41.787626     213 checks.go:132] validating if the "kubelet" service is enabled and active
I1007 23:19:41.798411     213 checks.go:205] validating availability of port 10250
I1007 23:19:41.798529     213 checks.go:205] validating availability of port 2379
I1007 23:19:41.798552     213 checks.go:205] validating availability of port 2380
... skipping 153 lines ...
I1007 23:20:23.440321     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:23.940292     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:24.440504     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] Initial timeout of 40s passed.
I1007 23:20:24.939566     213 round_trippers.go:454] GET https://172.17.0.2: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 23:20:25.440379     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:25.939496     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:26.440460     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:26.939420     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:27.440438     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:27.939406     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:28.440360     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:28.940305     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:29.440378     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:29.940255     213 round_trippers.go:454] GET https://172.17.0.2: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 23:20:30.439700     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:30.939472     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:31.440417     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:31.939460     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:32.439415     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:32.939409     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 23:20:37.940337     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:38.440442     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:38.940268     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:39.440193     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:39.939775     213 round_trippers.go:454] GET https://172.17.0.2: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 23:20:40.439452     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:40.940389     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:41.440374     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:41.940371     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:42.440285     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:42.940283     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 23:20:57.940315     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:58.440261     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:58.940269     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:59.440455     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:59.939471     213 round_trippers.go:454] GET https://172.17.0.2: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 23:21:00.440192     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:00.940342     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:01.440267     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:01.940329     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:02.440240     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:02.940359     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 23:21:37.939509     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:38.439364     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:38.940464     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:39.440435     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:39.939334     213 round_trippers.go:454] GET https://172.17.0.2: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 23:19:41.681538     213 initconfiguration.go:247] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
I1007 23:19:41.687506     213 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 23:19:41.727826     213 checks.go:372] validating the presence of executable ebtables
I1007 23:19:41.727864     213 checks.go:372] validating the presence of executable ethtool
I1007 23:19:41.727885     213 checks.go:372] validating the presence of executable socat
I1007 23:19:41.727928     213 checks.go:372] validating the presence of executable tc
I1007 23:19:41.727996     213 checks.go:372] validating the presence of executable touch
I1007 23:19:41.728046     213 checks.go:520] 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 23:19:41.732714     213 checks.go:403] checking whether the given node name is valid and reachable using net.LookupHost
I1007 23:19:41.732976     213 checks.go:618] validating kubelet version
I1007 23:19:41.787626     213 checks.go:132] validating if the "kubelet" service is enabled and active
I1007 23:19:41.798411     213 checks.go:205] validating availability of port 10250
I1007 23:19:41.798529     213 checks.go:205] validating availability of port 2379
I1007 23:19:41.798552     213 checks.go:205] validating availability of port 2380
... skipping 153 lines ...
I1007 23:20:23.440321     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:23.940292     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:24.440504     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] Initial timeout of 40s passed.
I1007 23:20:24.939566     213 round_trippers.go:454] GET https://172.17.0.2: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 23:20:25.440379     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:25.939496     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:26.440460     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:26.939420     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:27.440438     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:27.939406     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:28.440360     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:28.940305     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:29.440378     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:29.940255     213 round_trippers.go:454] GET https://172.17.0.2: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 23:20:30.439700     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:30.939472     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:31.440417     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:31.939460     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:32.439415     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:32.939409     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 23:20:37.940337     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:38.440442     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:38.940268     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:39.440193     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:39.939775     213 round_trippers.go:454] GET https://172.17.0.2: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 23:20:40.439452     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:40.940389     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:41.440374     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:41.940371     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:42.440285     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:42.940283     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 23:20:57.940315     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:58.440261     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:58.940269     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:59.440455     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:59.939471     213 round_trippers.go:454] GET https://172.17.0.2: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 23:21:00.440192     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:00.940342     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:01.440267     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:01.940329     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:02.440240     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:02.940359     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 23:21:37.939509     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:38.439364     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:38.940464     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:39.440435     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:39.939334     213 round_trippers.go:454] GET https://172.17.0.2: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 ...