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

Bug 1855491

Summary: [sriov] unlimit the max allowed mtu value in sriov network node policy
Product: OpenShift Container Platform Reporter: zenghui.shi <zshi>
Component: NetworkingAssignee: zenghui.shi <zshi>
Networking sub component: SR-IOV QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified    
Version: 4.6   
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1855492 1855493 (view as bug list) Environment:
Last Closed: 2020-10-27 16:13:32 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:
Bug Depends On:    
Bug Blocks: 1855492, 1855493    

Description zenghui.shi 2020-07-10 00:51:36 UTC
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 1 zhaozhanqi 2020-07-10 03:50:21 UTC
Verified this bug 

  - Vfs:
    - deviceID: 154c
      driver: iavf
      mtu: 9100
      pciAddress: 0000:3b:02.0
      vendor: "8086"
      vfID: 0
    - deviceID: 154c
      driver: iavf
      mtu: 9100
      pciAddress: 0000:3b:02.1
      vendor: "8086"
      vfID: 1

Comment 4 errata-xmlrpc 2020-10-27 16:13:32 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.6 GA Images), 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:4196