+++ 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:
Verified this bug on 4.5.0-202007211936.p0 VF mtu are inited correctly when PF and policy are same
typo. the csv version shoule be 4.5.0-202007220326.p0
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