Description of problem: After create some test pods, execute "ip a" on sdn pod, will find many errors "Error: Peer netns reference is invalid" Version-Release number of selected component (if applicable): 4.10.0-0.nightly-2021-12-23-153012 How reproducible: Frequently Steps to Reproduce: 1. Create some test pods oc exec sdn-vcjzd -n openshift-sdn --container=sdn -i -- bash -c ip addr show if460 veth03979c80 STDERR: Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. Error: Peer netns reference is invalid. 2. 3. Actual results: Expected results: No above errors Additional info:
I believe this is a consequence of the fix for https://bugzilla.redhat.com/show_bug.cgi?id=2003193. There may be files in /var/run/netns that have been unmounted as namespaces but remain as files. From the sound of it, this behavior is unacceptable? if so, I would deem this a blocker. Unfortunately, this has already been backported to 4.9 as well
fixed by a 4.10 variant of the attached PR
Tested on 4.10.0-0.nightly-2022-01-20-082726. Created and deleted test pods. Checked from sdn pod by listing the interface. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2022-01-20-082726 True False 70m Cluster version is 4.10.0-0.nightly-2022-01-20-082726
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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056