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

Bug 1855492

Summary:	[4.5][sriov] unlimit the max allowed mtu value in sriov network node policy
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 ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	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:	1855491
Clones:	1855496 (view as bug list)		Environment:
Last Closed:	2020-07-22 12:20:42 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:	1855491
Bug Blocks:	1855496

Description zenghui.shi 2020-07-10 00:54:13 UTC

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

Description of problem:


Currently SriovNetworkNodePolicy CRD limits the mtu value to be in the range of:
1 <= mtu <= 9000,  but user may want to set mtu outside of the allowed range, such as 9100. 

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

How reproducible:
always

Steps to Reproduce:
1. create a SriovNetworkNodePolicy CR with mtu set to 9100
2.
3.

Actual results:
SriovNetworkNodePolicy CR is rejected


Expected results:
SriovNetworkNodePolicy CR is accepted

Additional info:

Comment 6 zhaozhanqi 2020-07-16 03:02:14 UTC

Verified this bug on 4.5.0-202007160100.p0

apply policy with mtu is 9200 as below:

apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
  name: intel-netdevice
  namespace: openshift-sriov-network-operator
spec:
  deviceType: netdevice
  nicSelector:
    pfNames:
      - ens1f0
    rootDevices:
      - '0000:3b:00.0'
    vendor: '8086'
  nodeSelector:
    feature.node.kubernetes.io/sriov-capable: 'true'
  numVfs: 5
  mtu: 9200
  priority: 99
  resourceName: intelnetdevice


******************check the node state*****
  - Vfs:
    - deviceID: 154c
      driver: iavf
      mtu: 9200
      pciAddress: 0000:3b:02.0
      vendor: "8086"
      vfID: 0
    - deviceID: 154c
      driver: iavf
      mtu: 9200
      pciAddress: 0000:3b:02.1
      vendor: "8086"
      vfID: 1

Comment 8 errata-xmlrpc 2020-07-22 12:20:42 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:2956