Bug 2035969

Summary:	"ip a " shows "Error: Peer netns reference is invalid" after create test pods
Product:	OpenShift Container Platform	Reporter:	huirwang
Component:	Node	Assignee:	Peter Hunt <pehunt>
Node sub component:	CRI-O	QA Contact:	Sunil Choudhary <schoudha>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	medium	CC:	akaris, aos-bugs, diflores, dwalsh, mifiedle, moddi, zzhao
Version:	4.10
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2042451 2043180 (view as bug list)		Environment:
Last Closed:	2022-03-10 16:36:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2042451, 2043180

Description huirwang 2021-12-29 00:24:58 UTC

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:

Comment 4 Peter Hunt 2022-01-05 16:35:31 UTC

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

Comment 5 Peter Hunt 2022-01-05 18:25:43 UTC

fixed by a 4.10 variant of the attached PR

Comment 9 Sunil Choudhary 2022-01-21 09:42:18 UTC

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

Comment 13 errata-xmlrpc 2022-03-10 16:36:47 UTC

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