Bug 1854783

Summary:	[4.4.z][sriov] VF MTU cannot be set if the initial PF MTU equals to the MTU in the SriovNetworkNodePolicy CR
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:	zzhao
Version:	4.4
Target Milestone:	---
Target Release:	4.4.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1854781	Environment:
Last Closed:	2020-08-04 14:16:01 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:	1854781
Bug Blocks:	1854782

Description Peng Liu 2020-07-08 08:58:26 UTC

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

Description of problem:
VF MTU cannot be set if the initial PF MTU equals to the MTU in the SriovNetworkNodePolicy CR

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


How reproducible:


Steps to Reproduce:
1. Set MTU to a non-default value, e.g. $ ip link set dev ens803f0 mtu 5000
2. deploy the sriov network operator
3. apply the 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: 5000
  numVfs: 4
  nicSelector:
    pfNames: ['ens803f0']
  isRdma: false

Actual results:
The VFs were created with MTU 1500


Expected results:
The VFs were created with MTU 5000
Additional info:

Comment 4 zhaozhanqi 2020-07-30 05:56:22 UTC

Verified this bug on 4.4

Comment 6 errata-xmlrpc 2020-08-04 14:16:01 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 (OpenShift Container Platform 4.4.15 bug fix 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/RHBA-2020:3128