### Test report for 4757.2.2 / amd64 **Platforms tested** : akamai 🟢 ok **cl.basic**; Succeeded: akamai (1) 🟢 ok **cl.etcd-member.discovery**; Succeeded: akamai (1) 🟢 ok **cl.flannel.udp**; Succeeded: akamai (1) 🟢 ok **cl.flannel.vxlan**; Succeeded: akamai (1) 🟢 ok **cl.ignition.kargs**; Succeeded: akamai (1) 🟢 ok **cl.ignition.v2.btrfsroot**; Succeeded: akamai (1) 🟢 ok **cl.install.cloudinit**; Succeeded: akamai (1) 🟢 ok **cl.internet**; Succeeded: akamai (1) 🟢 ok **cl.network.initramfs.second-boot**; Succeeded: akamai (1) 🟢 ok **coreos.ignition.once**; Succeeded: akamai (1) 🟢 ok **coreos.ignition.resource.local**; Succeeded: akamai (1) 🟢 ok **coreos.ignition.resource.remote**; Succeeded: akamai (1) 🟢 ok **coreos.ignition.security.tls**; Succeeded: akamai (1) 🟢 ok **coreos.ignition.sethostname**; Succeeded: akamai (1) 🟢 ok **coreos.ignition.ssh.key**; Succeeded: akamai (1) 🟢 ok **docker.network-openbsd-nc**; Succeeded: akamai (1) 🟢 ok **kubeadm.v1.35.1.calico.base**; Succeeded: akamai (1) 🟢 ok **kubeadm.v1.35.1.cilium.base**; Succeeded: akamai (1) 🟢 ok **kubeadm.v1.35.1.flannel.base**; Succeeded: akamai (2); Failed: akamai (1)
                Diagnostic output for akamai, run 1 ``` L1: " Error: _cluster.go:125: I1021 16:54:38.051994 2011 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35" L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.9" L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.9" L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.9" L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.9" L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1" L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1" L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0" L9: "cluster.go:125: I1021 16:54:52.410395 2227 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.35" L10: "cluster.go:125: [init] Using Kubernetes version: v1.35.9" L11: "cluster.go:125: [preflight] Running pre-flight checks" L12: "cluster.go:125: [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_" L13: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster" L14: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection" L15: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_" L16: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__" L17: "cluster.go:125: [certs] Generating __ca__ certificate and key" L18: "cluster.go:125: [certs] Generating __apiserver__ certificate and key" L19: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-237-158-44 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172?.237.158.44]" L20: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key" L21: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key" L22: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key" L23: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation" L24: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation" L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation" L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation" L27: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation" L28: "cluster.go:125: [certs] Generating __sa__ key and public key" L29: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__" L30: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file" L31: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file" L32: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file" L33: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file" L34: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file" L35: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__" L36: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__" L37: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__" L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__" L39: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__" L40: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__" L41: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__" L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__" L43: "cluster.go:125: [kubelet-start] Starting the kubelet" L44: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__" L45: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s" L46: "cluster.go:125: [kubelet-check] The kubelet is healthy after 502.216564ms" L47: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s" L48: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.237.158.44:6443/livez" L49: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz" L50: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez" L51: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 2.065497922s" L52: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 23.045337551s" L53: "cluster.go:125: [control-plane-check] kube-apiserver is not healthy after 30m0.000257484s" L54: "cluster.go:125: " L55: "cluster.go:125: A control plane component may have crashed or exited when started by the container runtime." L56: "cluster.go:125: To troubleshoot, list all containers using your preferred container runtimes CLI." L57: "cluster.go:125: Here is one example how you may list all running Kubernetes containers by using crictl:" L58: "cluster.go:125: - _crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause_" L59: "cluster.go:125: Once you have found the failing container, you can inspect its logs with:" L60: "cluster.go:125: - _crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock logs CONTAINERID_" L61: "cluster.go:125: " L62: "cluster.go:125: error: error execution phase wait-control-plane: failed while waiting for the control plane to start: kube-apiserver check failed at https://172.237.158.44:6443/livez: Get __https://17?2.237.158.44:6443/livez?timeout=10s__: context deadline exceeded" L63: "cluster.go:125: To see the stack trace of this error execute with --v=5 or higher" L64: "kubeadm.go:197: unable to setup cluster: unable to run master script: Process exited with status 1_" L65: " " ```
🟢 ok **kubeadm.v1.36.1.calico.base**; Succeeded: akamai (1) 🟢 ok **kubeadm.v1.36.1.cilium.base**; Succeeded: akamai (1) 🟢 ok **kubeadm.v1.36.1.flannel.base**; Succeeded: akamai (1) 🟢 ok **kubeadm.v1.37.0.calico.base**; Succeeded: akamai (1) 🟢 ok **kubeadm.v1.37.0.cilium.base**; Succeeded: akamai (1) 🟢 ok **kubeadm.v1.37.0.flannel.base**; Succeeded: akamai (1) 🟢 ok **linux.nfs.v3**; Succeeded: akamai (1) 🟢 ok **linux.nfs.v4**; Succeeded: akamai (1)