Bug 1854778

Summary:	[sriov] [4.5] The operator reset the PF MTU to 1500 when policy is deleted
Product:	OpenShift Container Platform	Reporter:	Peng Liu <pliu>
Component:	Networking	Assignee:	Peng Liu <pliu>
Networking sub component:	SR-IOV	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	zshi, zzhao
Version:	4.5
Target Milestone:	---
Target Release:	4.5.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1854775	Environment:
Last Closed:	2020-07-30 18:56:59 UTC	Type:	---
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:	1854775
Bug Blocks:	1854779

Description Peng Liu 2020-07-08 08:44:17 UTC

+++ This bug was initially created as a clone of Bug #1854775 +++

Description of problem:
The operator always reset the PF MTU to 1500 when the policy is deleted

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


How reproducible:


Steps to Reproduce:
1. Set the PF mtu to 5000. e.g. $ sudo ip link set dev ens803f0 mtu 5000

2. Deploy the sriov network operator 

3. Apply following policy
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
  name: policy-net-2
spec:
  resourceName: nic2
  nodeSelector:
    kubernetes.io/hostname: worker-0
    feature.node.kubernetes.io/network-sriov.capable: "true"
  priority: 99
  mtu: 9000
  numVfs: 4
  nicSelector:
    pfNames: ['ens803f0#0-0']
  isRdma: false

4. remove the policy

Actual results:
The MTU of ens803f0 was reset to 1500

Expected results:
The MTU of ens803f0 was reset to 5000

Additional info:

Comment 5 zhaozhanqi 2020-07-22 07:25:25 UTC

Verified this bug on 4.5.0-202007211936.p0

MTU can be restored to origin when the policy is deleted.

Comment 7 errata-xmlrpc 2020-07-30 18:56:59 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, 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/RHBA-2020:3028