<p>Found the cause in journalctl of containerd.</p>
<pre><code>Jul 25 15:10:36 ubdock09 containerd[23164]: time=&quot;2022-07-25T15:10:36.480398235+02:00&quot; level=error msg=&quot;failed to reload cni configuration after receiving fs change event(\&quot;/etc/cni/net.d/.10-flannel.conf.swp\&quot;: REMOVE)&quot; error=&quot;cni config load failed: failed to load CNI config file /etc/cni/net.d/10-flannel.conf: error parsing configuration: missing 'type': invalid cni config: failed to load cni config&quot;
</code></pre>
<p>The Ready machines did not have /etc/cni/net.d/10-flannel.conf so I just removed the /etc/cni/net.d directory and the network device cni0 that was created by the container network interface.</p>
<pre><code>id@machine:/# ip -4 addr show
6: cni0: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 10.244.11.1/24 brd 10.244.11.255 scope global cni0
       valid_lft forever preferred_lft forever

ip link delete cni0
</code></pre>
<p>Then restarted containerd and the flannel pod. Now the node is ready and cni0 is recreated.</p>

CC BY-SA 4.0
2023-02-02T08:51:44.510Z
Hi Can you explain deleted cni0 with ip link delete cni0,
Ankur
CC BY-SA 4.0
2023-02-09T10:21:37.347Z
ok, there you go
Serve Laurijssen
CC BY-SA 4.0
2022-07-25T13:19:32.410Z
2023-02-09T10:20:58.300Z
2023-02-09T10:20:58.300Z
Serve Laurijssen
<p>We have a cluster with 4 worker nodes and 1 master, and the flannel CNI installed. 1 kube-flannel-ds-xxxx pod running on every node.</p>
<p>They used to run fine, but 1 node suddenly entered NotReady state and does not come out of it anymore.</p>
<p>journalctl -u kubelet -f on the node constanly emits &quot;cni plugin not initialized&quot;</p>
<pre><code>Jul 25 14:44:05 ubdock09 kubelet[13076]: E0725 14:44:05.916280   13076 kubelet.go:2349] &quot;Container runtime network not ready&quot; networkReady=&quot;NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized&quot;
</code></pre>
<p>Deleting the flannel pod makes a new one start up but the pluin keeps being uninitialized.
What can we do or check to fix this?</p>

<docker><kubernetes>
NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized
Serve Laurijssen
# NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

(Asked by: username_0 on 2022-07-25)

We have a cluster with 4 worker nodes and 1 master, and the flannel CNI installed. 1 kube-flannel-ds-xxxx pod running on every node.
They used to run fine, but 1 node suddenly entered NotReady state and does not come out of it anymore.
journalctl -u kubelet -f on the node constanly emits "cni plugin not initialized"
Jul 25 14:44:05 ubdock09 kubelet[13076]: E0725 14:44:05.916280   13076 kubelet.go:2349] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"

Deleting the flannel pod makes a new one start up but the pluin keeps being uninitialized.
What can we do or check to fix this?

**Tags:** docker, kubernetes


---

## 1 answers

### Answer by username_0 on 2022-07-25. Score: 6 | Accepted answer

Found the cause in journalctl of containerd.
Jul 25 15:10:36 ubdock09 containerd[23164]: time="2022-07-25T15:10:36.480398235+02:00" level=error msg="failed to reload cni configuration after receiving fs change event(\"/etc/cni/net.d/.10-flannel.conf.swp\": REMOVE)" error="cni config load failed: failed to load CNI config file /etc/cni/net.d/10-flannel.conf: error parsing configuration: missing 'type': invalid cni config: failed to load cni config"

The Ready machines did not have /etc/cni/net.d/10-flannel.conf so I just removed the /etc/cni/net.d directory and the network device cni0 that was created by the container network interface.
id@machine:/# ip -4 addr show
6: cni0:  mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 10.244.11.1/24 brd 10.244.11.255 scope global cni0
       valid_lft forever preferred_lft forever

ip link delete cni0

Then restarted containerd and the flannel pod. Now the node is ready and cni0 is recreated.

> **Comments:**
> **username_1**: Hi Can you explain deleted cni0 with ip link delete cni0,  
> **username_0**: ok, there you go  

---

