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
Elapsed3m24s
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.4: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
discovery:
  bootstrapToken:
    apiServerEndpoint: 172.17.0.4: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.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
controlPlane:
  localAPIEndpoint:
    advertiseAddress: 172.17.0.4
... 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.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.4: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:43.455486     214 checks.go:377] validating the presence of executable ebtables
I1007 23:19:43.455539     214 checks.go:377] validating the presence of executable ethtool
I1007 23:19:43.455568     214 checks.go:377] validating the presence of executable socat
I1007 23:19:43.455618     214 checks.go:377] validating the presence of executable tc
I1007 23:19:43.455848     214 checks.go:377] validating the presence of executable touch
I1007 23:19:43.455902     214 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 23:19:43.460552     214 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
I1007 23:19:43.460984     214 checks.go:623] validating kubelet version
I1007 23:19:43.524967     214 checks.go:129] validating if the "kubelet" service is enabled and active
I1007 23:19:43.537317     214 checks.go:202] validating availability of port 10250
I1007 23:19:43.537459     214 checks.go:202] validating availability of port 2379
I1007 23:19:43.537524     214 checks.go:202] validating availability of port 2380
... skipping 152 lines ...
I1007 23:20:27.290436     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:27.790408     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:28.290402     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:28.789681     214 round_trippers.go:454] GET https://172.17.0.4: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 23:20:29.290497     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:29.790509     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:30.290441     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:30.790453     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:31.290457     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:31.790304     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:32.290367     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:32.790302     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:33.290565     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:33.789656     214 round_trippers.go:454] GET https://172.17.0.4: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:34.289732     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:34.790532     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:35.290612     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:35.789588     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:36.290500     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:36.790358     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 23:20:41.790602     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:42.290651     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:42.790614     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:43.289824     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:43.789828     214 round_trippers.go:454] GET https://172.17.0.4: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:44.291176     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:44.790313     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:45.290363     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:45.790615     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:46.289978     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:46.790348     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 23:21:01.789684     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:02.289638     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:02.790093     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:03.289905     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:03.790301     214 round_trippers.go:454] GET https://172.17.0.4: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:04.289689     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:04.789609     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:05.289561     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:05.790484     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:06.289880     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:06.791222     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 23:21:41.789632     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:42.289558     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:42.790281     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:43.290173     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:43.790346     214 round_trippers.go:454] GET https://172.17.0.4: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:43.404739     214 initconfiguration.go:246] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
I1007 23:19:43.415715     214 kubelet.go:259] setting the KubeletConfiguration cgroupDriver to "systemd"
[init] Using Kubernetes version: v1.21.2
... skipping 23 lines ...
I1007 23:19:43.455486     214 checks.go:377] validating the presence of executable ebtables
I1007 23:19:43.455539     214 checks.go:377] validating the presence of executable ethtool
I1007 23:19:43.455568     214 checks.go:377] validating the presence of executable socat
I1007 23:19:43.455618     214 checks.go:377] validating the presence of executable tc
I1007 23:19:43.455848     214 checks.go:377] validating the presence of executable touch
I1007 23:19:43.455902     214 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 23:19:43.460552     214 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
I1007 23:19:43.460984     214 checks.go:623] validating kubelet version
I1007 23:19:43.524967     214 checks.go:129] validating if the "kubelet" service is enabled and active
I1007 23:19:43.537317     214 checks.go:202] validating availability of port 10250
I1007 23:19:43.537459     214 checks.go:202] validating availability of port 2379
I1007 23:19:43.537524     214 checks.go:202] validating availability of port 2380
... skipping 152 lines ...
I1007 23:20:27.290436     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:27.790408     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:28.290402     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:28.789681     214 round_trippers.go:454] GET https://172.17.0.4: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 23:20:29.290497     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:29.790509     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:30.290441     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:30.790453     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:31.290457     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:31.790304     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:32.290367     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:32.790302     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:33.290565     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:33.789656     214 round_trippers.go:454] GET https://172.17.0.4: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:34.289732     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:34.790532     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:35.290612     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:35.789588     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:36.290500     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:36.790358     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 23:20:41.790602     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:42.290651     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:42.790614     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:43.289824     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:43.789828     214 round_trippers.go:454] GET https://172.17.0.4: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:44.291176     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:44.790313     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:45.290363     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:45.790615     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:46.289978     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:20:46.790348     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 23:21:01.789684     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:02.289638     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:02.790093     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:03.289905     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:03.790301     214 round_trippers.go:454] GET https://172.17.0.4: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:04.289689     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:04.789609     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:05.289561     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:05.790484     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:06.289880     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:06.791222     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 23:21:41.789632     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:42.289558     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:42.790281     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:43.290173     214 round_trippers.go:454] GET https://172.17.0.4:6443/healthz?timeout=10s  in 0 milliseconds
I1007 23:21:43.790346     214 round_trippers.go:454] GET https://172.17.0.4: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 ...