# Kubeadm init with failed node error

**URL:** <https://discuss.kubernetes.io/t/kubeadm-init-with-failed-node-error/20042>\
**Category:** General Discussions\
**Tags:** development\
**Created:** [May 17, 2022, 6:58am UTC](https://discuss.kubernetes.io/t/kubeadm-init-with-failed-node-error/20042 "2022-05-17T06:58:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![goodtry2](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@goodtry2](https://discuss.kubernetes.io/u/goodtry2)\
**Post date:** [May 17, 2022, 6:58am UTC](https://discuss.kubernetes.io/t/kubeadm-init-with-failed-node-error/20042/1 "2022-05-17T06:58:03Z")

</div>

![image](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/0/0dbe42e6e3e2b7c265a7684ecce8262fdf7e4b7a.png)

i am using ubuntu server.  
when running kubeadm init, i had the errors showing in the screenshot (have also provided the kubeadm version in the screenshot). The error looks like  
May 17 06:44:44 node1 kubelet[1965]: E0517 06:44:44.563519 1965 kubelet.go:2419] “Error getting node” err=“node “node1” not found”  
May 17 06:44:44 node1 kubelet[1965]: E0517 06:44:44.664897 1965 kubelet.go:2419] “Error getting node” err=“node “node1” not found”  
May 17 06:44:44 node1 kubelet[1965]: E0517 06:44:44.765447 1965 kubelet.go:2419] “Error getting node” err=“node “node1” not found”

but i am not sure if this is the root cause for the problem. Can any one help on this?

---

<div class="post-metadata">

**Author:** ![goodtry2](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@goodtry2](https://discuss.kubernetes.io/u/goodtry2)\
**Post date:** [May 17, 2022, 6:58am UTC](https://discuss.kubernetes.io/t/kubeadm-init-with-failed-node-error/20042/2 "2022-05-17T06:58:38Z")

</div>

![image](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/2/2aa6ae47dbd4fea8430bc07d2965604fe2f632c0.png)

---

<div class="post-metadata">

**Author:** ![goodtry2](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@goodtry2](https://discuss.kubernetes.io/u/goodtry2)\
**Post date:** [May 17, 2022, 6:58am UTC](https://discuss.kubernetes.io/t/kubeadm-init-with-failed-node-error/20042/3 "2022-05-17T06:58:59Z")

</div>

![image](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/c/cc1fd34cfaae18527df99415eaf35f2c8b1d8fc4.png)

---

<div class="post-metadata">

**Author:** ![alialp](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/alialp/32/10168_2.png) [@alialp](https://discuss.kubernetes.io/u/alialp)\
**Post date:** [May 27, 2022, 2:01pm UTC](https://discuss.kubernetes.io/t/kubeadm-init-with-failed-node-error/20042/4 "2022-05-27T14:01:09Z")

</div>

This is happening when your control-plane is not accessible which is sounds weird if you are already setting up the control-plane 🙂

- If you are using proxy to access outside word set NO\_PROXY in your systemctl env
- allow traffic in firewall

---

<div class="post-metadata">

**Author:** ![hiondal](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/hiondal/32/10624_2.png) [@hiondal](https://discuss.kubernetes.io/u/hiondal)\
**Post date:** [August 12, 2022, 6:59am UTC](https://discuss.kubernetes.io/t/kubeadm-init-with-failed-node-error/20042/5 "2022-08-12T06:59:57Z")

</div>

Solved for vanilla kubernetes with CRI-O as container runtime.

Causes:  
I guess it’s because of lack some module during install CRI-O. maybe runc module.  
It might be bug of CRI-O install package.

Workaround:

- Install CRIO and start it.
- Install docker to install runc perfectly.

```auto
# yum install -y yum-utils device-mapper-persistent-data lvm2
# yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
# yum install docker-ce -y

```

- When you init k8s cluster using kubeadm, add ‘–cri-socket’ option as followed.  
ex)  
kubeadm init   
–kubernetes-version=v1.23.1   
–pod-network-cidr=192.168.0.0/16   
–apiserver-advertise-address=10.193.229.141   
–cri-socket /var/run/crio/crio.sock