Description of problem: After reboot the worker server. the exist VF disappeared. Version-Release number of selected component (if applicable): quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.3.0-201912060615-ose-sriov-network-operator How reproducible: always Steps to Reproduce: 1. setup cluster and install sriov operator 2. init the Vf with sriovnetwork apiVersion: sriovnetwork.openshift.io/v1 kind: SriovNetworkNodePolicy metadata: name: intel-netdevice namespace: openshift-sriov-network-operator spec: deviceType: netdevice mtu: 1500 nicSelector: pfNames: - ens1f0 rootDevices: - '0000:3b:00.0' vendor: '8086' nodeSelector: feature.node.kubernetes.io/sriov-capable: 'true' numVfs: 5 priority: 99 resourceName: intelnetdevice 3. Check the VF status oc get sriovnetworknodestates.sriovnetwork.openshift.io node -o yaml 4. Reboot the worker 5. After the worker is started 6. Check the VF status again Actual results: step 6. the exist VF disappeared Expected results: exist VF should work well after worker restart. Additional info: re-created the config daemon pod can restore the VF
PR https://github.com/openshift/sriov-network-operator/pull/136 merged
Verified this bug, the Vf can work well when the worker reboot
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:0581