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 21:06
Elapsed3m24s
Revisionea0cd76fea8395c85a7d9e56c172dd1c47f2ec9c
Refs 2371

No Test Failures!


Error lines from build-log.txt

... skipping 123 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.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.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 21:07:30.953472     216 checks.go:377] validating the presence of executable ebtables
I1007 21:07:30.953547     216 checks.go:377] validating the presence of executable ethtool
I1007 21:07:30.953599     216 checks.go:377] validating the presence of executable socat
I1007 21:07:30.954108     216 checks.go:377] validating the presence of executable tc
I1007 21:07:30.954153     216 checks.go:377] validating the presence of executable touch
I1007 21:07:30.954195     216 checks.go:525] running all checks
	[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1046-gke\n", err: exit status 1
I1007 21:07:30.960872     216 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1046-gke
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
... skipping 161 lines ...
I1007 21:08:13.578420     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:14.079117     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:14.579201     216 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 21:08:15.078577     216 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 21:08:15.578705     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:16.078904     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:16.578785     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:17.081455     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:17.578531     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:18.079341     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:18.579342     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:19.079302     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:19.579421     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:20.078596     216 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 21:08:20.579251     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:21.079304     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:21.579529     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:22.078486     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:22.579400     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:23.079326     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 21:08:28.078698     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:28.578772     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:29.078937     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:29.578904     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:30.079033     216 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 21:08:30.578466     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:31.078631     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:31.578536     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:32.078544     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:32.579025     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:33.079082     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 21:08:48.078596     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:48.578604     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:49.078475     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:49.578460     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:50.078556     216 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 21:08:50.579344     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:51.079417     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:51.579376     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:52.079364     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:52.578379     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:53.078322     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 21:09:28.079349     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:09:28.579344     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:09:29.079274     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:09:29.579348     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:09:30.078387     216 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 21:07:30.902265     216 initconfiguration.go:246] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
I1007 21:07:30.914642     216 kubelet.go:259] setting the KubeletConfiguration cgroupDriver to "systemd"
[init] Using Kubernetes version: v1.21.2
... skipping 23 lines ...
I1007 21:07:30.953472     216 checks.go:377] validating the presence of executable ebtables
I1007 21:07:30.953547     216 checks.go:377] validating the presence of executable ethtool
I1007 21:07:30.953599     216 checks.go:377] validating the presence of executable socat
I1007 21:07:30.954108     216 checks.go:377] validating the presence of executable tc
I1007 21:07:30.954153     216 checks.go:377] validating the presence of executable touch
I1007 21:07:30.954195     216 checks.go:525] running all checks
	[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1046-gke\n", err: exit status 1
I1007 21:07:30.960872     216 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1046-gke
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
... skipping 161 lines ...
I1007 21:08:13.578420     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:14.079117     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:14.579201     216 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 21:08:15.078577     216 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 21:08:15.578705     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:16.078904     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:16.578785     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:17.081455     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:17.578531     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:18.079341     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:18.579342     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:19.079302     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:19.579421     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:20.078596     216 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 21:08:20.579251     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:21.079304     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:21.579529     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:22.078486     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:22.579400     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:23.079326     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1007 21:08:28.078698     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:28.578772     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:29.078937     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:29.578904     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:30.079033     216 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 21:08:30.578466     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:31.078631     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:31.578536     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:32.078544     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:32.579025     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:33.079082     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1007 21:08:48.078596     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:48.578604     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:49.078475     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:49.578460     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:50.078556     216 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 21:08:50.579344     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:51.079417     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:51.579376     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:52.079364     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:52.578379     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:08:53.078322     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1007 21:09:28.079349     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:09:28.579344     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:09:29.079274     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:09:29.579348     216 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1007 21:09:30.078387     216 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 ...