Pods running on the OpenShift node failed with error "Statfs "/proc/xxxxx/ns/net": no such file or directory".

Solution Unverified - Updated -

Issue

  • One found that pods running on the OpenShift node failed with below errors in atomic-openshift-node logs:
Dec 22 21:37:26 node1 atomic-openshift-node[2963]: W1222 21:37:26.037706    2963 cni.go:243] CNI failed to retrieve network namespace path: cannot find network namespace for the terminated container "xxxx"
Dec 22 21:37:26 node1 atomic-openshift-node[2963]: W1222 21:37:26.091780    2963 cni.go:243] CNI failed to retrieve network namespace path: cannot find network namespace for the terminated container "xxxx"
Dec 22 21:37:26 node1 atomic-openshift-node[2963]: E1222 21:37:26.482644    2963 cni.go:260] Error adding network: failed to Statfs "/proc/xxxx/ns/net": no such file or directory
Dec 22 21:37:26 node1 atomic-openshift-node[2963]: E1222 21:37:26.482669    2963 cni.go:221] Error while adding to cni lo network: failed to Statfs "/proc/xxxx/ns/net": no such file or directory
  • One tried to follow this solution, however it didn't resolve issue.

  • One also tried to reboot the faulty OpenShift node but the problem persists.

  • As a last resort one set the Selinux mode to permissive in order to allow the access to the resource /proc/xxxx/ns/net however that is not a correct configuration.

Environment

  • RHEL
    • 7.x
  • OpenShift Container Platform
    • 3.11.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In