Bug 1816912 - VF spoofChk is turned on automatically after releasing from SR-IOV pod
Summary: VF spoofChk is turned on automatically after releasing from SR-IOV pod
Keywords:
Status: CLOSED DUPLICATE of bug 1826592
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.0
Assignee: zenghui.shi
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-25 04:38 UTC by zenghui.shi
Modified: 2020-05-06 13:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-06 13:04:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.