kubeadm init error

pavell16

Hello @chrispokorni,

i have 3 VM and i am trying to initiate a cluster in a master node wit the command "sudo kubeadm init --pod-network-cidr=10.255.0.0/16" but always gives me the same output:

[init] Using Kubernetes version: v1.30.1
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR CRI]: container runtime is not running: output: E0608 20:43:47.700011 2580 remote_runtime.go:633] "Status from runtime service failed" err="rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
time="2024-06-08T20:43:47Z" level=fatal msg="getting status of runtime: rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
To see the stack trace of this error execute with --v=5 or higher

i have tried to check all the config files and modules but nothing seems to be working.

I have tried to restart kubelet but it says it is active but with various errors

● kubelet.service - kubelet: The Kubernetes Node Agent
Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/kubelet.service.d
└─10-kubeadm.conf
Active: active (running) since Sat 2024-06-08 22:13:05 UTC; 1min 33s ago
Docs: https://kubernetes.io/docs/
Main PID: 7377 (kubelet)
Tasks: 10 (limit: 2256)
Memory: 16.3M
CGroup: /system.slice/kubelet.service
└─7377 /usr/bin/kubelet

jun 08 22:14:21 k8scp kubelet[7377]: E0608 22:14:21.828859 7377 kubelet.go:2361] "Skipping pod synchronization" err="container runtime status check may not have completed yet"
jun 08 22:14:25 k8scp kubelet[7377]: E0608 22:14:25.598875 7377 remote_runtime.go:633] "Status from runtime service failed" err="rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
jun 08 22:14:25 k8scp kubelet[7377]: E0608 22:14:25.599130 7377 kubelet.go:2885] "Container runtime sanity check failed" err="rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
jun 08 22:14:26 k8scp kubelet[7377]: E0608 22:14:26.830953 7377 kubelet.go:2361] "Skipping pod synchronization" err="container runtime status check may not have completed yet"
jun 08 22:14:30 k8scp kubelet[7377]: E0608 22:14:30.601134 7377 remote_runtime.go:633] "Status from runtime service failed" err="rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
jun 08 22:14:30 k8scp kubelet[7377]: E0608 22:14:30.601192 7377 kubelet.go:2885] "Container runtime sanity check failed" err="rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
jun 08 22:14:31 k8scp kubelet[7377]: E0608 22:14:31.834838 7377 kubelet.go:2361] "Skipping pod synchronization" err="container runtime status check may not have completed yet"
jun 08 22:14:35 k8scp kubelet[7377]: E0608 22:14:35.612249 7377 remote_runtime.go:633] "Status from runtime service failed" err="rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
jun 08 22:14:35 k8scp kubelet[7377]: E0608 22:14:35.614753 7377 kubelet.go:2885] "Container runtime sanity check failed" err="rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
jun 08 22:14:36 k8scp kubelet[7377]: E0608 22:14:36.847148 7377 kubelet.go:2361] "Skipping pod synchronization" err="container runtime status check may not have completed yet"

Please help i am desperate.

chrispokorni

Hello @pavell16,

The "various errors" you see are quite descriptive. There are close to a dozen errors, all referring to the container runtime. Have you installed the runtime on each VM? The container runtime installation for the control plane VM is described by steps 12 and 13 in lab exercise 3.1. Those are the steps that can help to validate the successful installation and configuration of the containerd container runtime.

Are your VMs sized accordingly? Are you running the recommended guest OS? Are the firewalls allowing all inbound traffic to all ports, all protocols from all sources? Are you installing the recommended Kubernetes version? Is the network plugin using the same CIDR as supplied by your init command?

Regards,
-Chris