Bug 1782144

Summary: [sriov] The exist VF disappeared when worker reboot
Product: OpenShift Container Platform Reporter: Peng Liu <pliu>
Component: NetworkingAssignee: Feng Pan <fpan>
Networking sub component: SR-IOV QA Contact: zhaozhanqi <zzhao>
Status: CLOSED NOTABUG Docs Contact:
Severity: unspecified    
Priority: unspecified    
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-11 09:28:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peng Liu 2019-12-11 09:25:33 UTC 
This bug was initially created as a copy of Bug #1781718

I am copying this bug because: 



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