+++ 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:
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
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