Description of problem: vfio-pci driver cannot be loaded to VF if the config daemon is interrupt during draining node Version-Release number of selected component (if applicable): 4.5 How reproducible: A freshly installed worker node, which hasn't been configured with any vfio-pci driver. Steps to Reproduce: 1. Apply following SriovNetworkNodePolicy CR with driverType vfio-pci. --- apiVersion: sriovnetwork.openshift.io/v1 kind: SriovNetworkNodePolicy metadata: name: policy-mlx-1 spec: resourceName: nicmlx1 nodeSelector: feature.node.kubernetes.io/network-sriov.capable: "true" priority: 99 # isRdma: true numVfs: 4 nicSelector: vendor: "15b3" pfNames: ['ens785f0#0-2'] rootDevices: ['0000:18:00.0'] deviceType: "vfio-pci" 2. Kill the sriov-network-config-daemon pod when it starts to drain the node. 3. Actual results: The node reboot is not triggered. sriov-network-config-daemon pod keeps restarting, and the vfio-pci driver cannot be bind to the VFs. Expected results: The node shall reboot, and the vfio-pci driver shall be bind to the VFs successfully. Additional info:
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:2409