+++ This bug was initially created as a clone of Bug #1854775 +++ Description of problem: The operator always reset the PF MTU to 1500 when the policy is deleted Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Set the PF mtu to 5000. e.g. $ sudo ip link set dev ens803f0 mtu 5000 2. Deploy the sriov network operator 3. Apply 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: 9000 numVfs: 4 nicSelector: pfNames: ['ens803f0#0-0'] isRdma: false 4. remove the policy Actual results: The MTU of ens803f0 was reset to 1500 Expected results: The MTU of ens803f0 was reset to 5000 Additional info:
Verified this bug on v4.4.0.202007232108.p0-8 1. setup the cluster 2. set the MTU of one interface on node eg. ip link set dev ens1f0 mtu 9000 3. Setup the sriov operaotr 4. Create one policy with MTU is 9200 5. Check the MTU of VF and PF are changed to 9200 6. Delete the policy 7. check the MTU of PF back to 9000.
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