Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1816912

Summary:	VF spoofChk is turned on automatically after releasing from SR-IOV pod
Product:	OpenShift Container Platform	Reporter:	zenghui.shi <zshi>
Component:	Networking	Assignee:	zenghui.shi <zshi>
Networking sub component:	SR-IOV	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	bbennett
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-06 13:04:59 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:

Description zenghui.shi 2020-03-25 04:38:53 UTC

Description of problem:

VF properties (such as vlan, spoof check, link state etc) are defined in net-attach-def and applied to VF when it's moved to container namespace by SR-IOV CNI. In case no values are specified in net-attach-def for VF properties, SR-IOV CNI won't configure it when cmdAdd is invoked but always restore to a 'default' value when cmdDel is called. The 'default' value for spoof check is 'on'

This causes problem for Mellanox VF as it has a different default value `off`.
The subsequencial use of the same VF (with spoofChk set to on) will block traffic from going out of container via SR-IOV VF.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 zenghui.shi 2020-05-06 13:04:59 UTC


*** This bug has been marked as a duplicate of bug 1826592 ***