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
Elapsed3m34s
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.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 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.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 35 lines ...
I1008 01:24:29.378643     213 checks.go:377] validating the presence of executable ebtables
I1008 01:24:29.378740     213 checks.go:377] validating the presence of executable ethtool
I1008 01:24:29.378782     213 checks.go:377] validating the presence of executable socat
I1008 01:24:29.378825     213 checks.go:377] validating the presence of executable tc
I1008 01:24:29.378930     213 checks.go:377] validating the presence of executable touch
I1008 01:24:29.378996     213 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
I1008 01:24:29.385868     213 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 ...
I1008 01:25:11.950392     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:12.449322     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:12.950410     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.
I1008 01:25:13.449782     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.
I1008 01:25:13.949320     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:14.450430     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:14.949567     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:15.449669     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:15.949592     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:16.449562     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:16.949479     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:17.449435     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:17.949379     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:18.449547     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.
I1008 01:25:18.951239     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 1 milliseconds
I1008 01:25:19.450239     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:19.950183     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:20.450246     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:20.950261     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:21.450527     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1008 01:25:26.450342     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:26.950496     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:27.449317     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:27.950563     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:28.449519     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.
I1008 01:25:28.950369     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:29.449607     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:29.949419     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:30.449499     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:30.949425     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:31.450511     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1008 01:25:46.449613     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:46.949667     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:47.449600     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:47.949509     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:48.449597     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.
I1008 01:25:48.950008     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:49.450435     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:49.950766     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:50.449745     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:50.949693     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:51.449448     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1008 01:26:26.449574     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:26.949655     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:27.449449     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:27.949491     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:28.449734     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:
I1008 01:24:29.321320     213 initconfiguration.go:246] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
[init] Using Kubernetes version: v1.21.2
I1008 01:24:29.336740     213 kubelet.go:259] setting the KubeletConfiguration cgroupDriver to "systemd"
... skipping 23 lines ...
I1008 01:24:29.378643     213 checks.go:377] validating the presence of executable ebtables
I1008 01:24:29.378740     213 checks.go:377] validating the presence of executable ethtool
I1008 01:24:29.378782     213 checks.go:377] validating the presence of executable socat
I1008 01:24:29.378825     213 checks.go:377] validating the presence of executable tc
I1008 01:24:29.378930     213 checks.go:377] validating the presence of executable touch
I1008 01:24:29.378996     213 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
I1008 01:24:29.385868     213 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 ...
I1008 01:25:11.950392     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:12.449322     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:12.950410     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.
I1008 01:25:13.449782     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.
I1008 01:25:13.949320     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:14.450430     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:14.949567     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:15.449669     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:15.949592     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:16.449562     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:16.949479     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:17.449435     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:17.949379     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:18.449547     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.
I1008 01:25:18.951239     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 1 milliseconds
I1008 01:25:19.450239     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:19.950183     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:20.450246     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:20.950261     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:21.450527     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 9 lines ...
I1008 01:25:26.450342     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:26.950496     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:27.449317     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:27.950563     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:28.449519     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.
I1008 01:25:28.950369     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:29.449607     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:29.949419     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:30.449499     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:30.949425     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:31.450511     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 29 lines ...
I1008 01:25:46.449613     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:46.949667     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:47.449600     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:47.949509     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:48.449597     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.
I1008 01:25:48.950008     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:49.450435     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:49.950766     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:50.449745     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:50.949693     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:25:51.449448     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
... skipping 69 lines ...
I1008 01:26:26.449574     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:26.949655     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:27.449449     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:27.949491     213 round_trippers.go:454] GET https://172.17.0.2:6443/healthz?timeout=10s  in 0 milliseconds
I1008 01:26:28.449734     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 ...