Description of problem:
Messages files are getting full with messages:
StopPodSandbox $SHA from runtime service failed: rpc error: code = 2 desc = NetworkPlugin cni failed to teardown pod <pod-name> network: CNI failed to retrieve network namespace path: Error: No such container: $SHA
Pods no longer exist in the nodes, and there's no reference to them in etcd
Doing a rm -rf /var/lib/docker doesn't solve the problem
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Too many error messages are logged for pods that no longer exist
"NetworkPlugin cni failed to teardown pod ... " messages are not logged
Upstream issue: https://github.com/kubernetes/kubernetes/issues/44307
This should fix the issue, or we need a chain of backports from upstream.
(In reply to Rajat Chopra from comment #1)
> This should fix the issue, or we need a chain of backports from upstream.
Thanks Rajat, any idea if there is a workaround we could apply now?
Javier, unfortunately no workaround there.
Tested on OCP build v3.7.0-0.190.0
Issue has been fixed.
There will be no error messages in the atomic-openshift-node log when deleting the docker container which is created as hostnetwork enabled pod.
With the same steps, the error messages appear in the node log as below on build prior 3.7.0-0.190.0.
Nov 03 03:51:14 qe-bmeng.interna atomic-openshift-node: W1103 03:51:14.541341 23194 cni.go:258] CNI failed to retrieve network namespace path: Error: No such container: c5e769d5f72ef91c44e50f9eb6a73a74ce92372e5a705a3edf941a38bec60454
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.