Bug 1822202

Summary:	vfio-pci driver cannot be loaded to VF if the config daemon is interrupt during draining node
Product:	OpenShift Container Platform	Reporter:	Peng Liu <pliu>
Component:	Networking	Assignee:	Peng Liu <pliu>
Networking sub component:	SR-IOV	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1822543 1822546 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:26:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1822543

Description Peng Liu 2020-04-08 13:36:41 UTC

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:

Comment 4 errata-xmlrpc 2020-07-13 17:26:16 UTC

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