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-08 01:23
Elapsed3m40s
Revisionea0cd76fea8395c85a7d9e56c172dd1c47f2ec9c
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.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.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.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 ...
I1008 01:24:38.801558     213 checks.go:372] validating the presence of executable ebtables
I1008 01:24:38.801669     213 checks.go:372] validating the presence of executable ethtool
I1008 01:24:38.801754     213 checks.go:372] validating the presence of executable socat
I1008 01:24:38.801807     213 checks.go:372] validating the presence of executable tc
I1008 01:24:38.801835     213 checks.go:372] validating the presence of executable touch
I1008 01:24:38.801871     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
I1008 01:24:38.807378     213 checks.go:403] checking whether the given node name is valid and reachable using net.LookupHost
I1008 01:24:38.807653     213 checks.go:618] validating kubelet version
I1008 01:24:38.882074     213 checks.go:132] validating if the "kubelet" service is enabled and active
I1008 01:24:38.894578     213 checks.go:205] validating availability of port 10250
I1008 01:24:38.894759     213 checks.go:205] validating availability of port 2379
I1008 01:24:38.894932     213 checks.go:205] validating availability of port 2380
... skipping 153 lines ...
I1008 01:25:21.618027     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:22.118022     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:22.618026     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.
I1008 01:25:23.118107     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.
I1008 01:25:23.618056     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:24.118159     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:24.619209     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:25.118064     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:25.619189     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:26.119139     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:26.617925     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:27.118922     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:27.618821     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:28.118629     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.
I1008 01:25:28.618852     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:29.118834     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:29.618917     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:30.118813     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:30.618683     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:31.118857     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1008 01:25:36.118031     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:36.618311     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:37.118220     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:37.618164     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:38.118107     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.
I1008 01:25:38.618353     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:39.118579     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:39.618432     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:40.118335     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:40.618271     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:41.118050     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1008 01:25:56.118869     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:56.618993     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:57.120750     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 1 milliseconds
I1008 01:25:57.618075     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:58.118679     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.
I1008 01:25:58.618942     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:59.118868     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:59.618914     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:00.118898     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:00.619137     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:01.118045     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1008 01:26:36.119098     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:36.618039     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:37.119052     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:37.618926     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:38.118931     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:
I1008 01:24:38.738457     213 initconfiguration.go:247] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
I1008 01:24:38.745144     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 ...
I1008 01:24:38.801558     213 checks.go:372] validating the presence of executable ebtables
I1008 01:24:38.801669     213 checks.go:372] validating the presence of executable ethtool
I1008 01:24:38.801754     213 checks.go:372] validating the presence of executable socat
I1008 01:24:38.801807     213 checks.go:372] validating the presence of executable tc
I1008 01:24:38.801835     213 checks.go:372] validating the presence of executable touch
I1008 01:24:38.801871     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
I1008 01:24:38.807378     213 checks.go:403] checking whether the given node name is valid and reachable using net.LookupHost
I1008 01:24:38.807653     213 checks.go:618] validating kubelet version
I1008 01:24:38.882074     213 checks.go:132] validating if the "kubelet" service is enabled and active
I1008 01:24:38.894578     213 checks.go:205] validating availability of port 10250
I1008 01:24:38.894759     213 checks.go:205] validating availability of port 2379
I1008 01:24:38.894932     213 checks.go:205] validating availability of port 2380
... skipping 153 lines ...
I1008 01:25:21.618027     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:22.118022     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:22.618026     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.
I1008 01:25:23.118107     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.
I1008 01:25:23.618056     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:24.118159     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:24.619209     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:25.118064     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:25.619189     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:26.119139     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:26.617925     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:27.118922     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:27.618821     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:28.118629     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.
I1008 01:25:28.618852     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:29.118834     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:29.618917     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:30.118813     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:30.618683     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:31.118857     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1008 01:25:36.118031     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:36.618311     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:37.118220     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:37.618164     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:38.118107     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.
I1008 01:25:38.618353     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:39.118579     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:39.618432     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:40.118335     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:40.618271     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:41.118050     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1008 01:25:56.118869     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:56.618993     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:57.120750     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 1 milliseconds
I1008 01:25:57.618075     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:58.118679     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.
I1008 01:25:58.618942     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:59.118868     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:59.618914     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:00.118898     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:00.619137     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:01.118045     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1008 01:26:36.119098     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:36.618039     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:37.119052     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:37.618926     213 round_trippers.go:454] GET https://172.17.0.5:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:38.118931     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 ...