Description of problem:
Given the sriov operator is installed by operator hub
When creating SriovNetworkNodePolicy CR on xxv710, then sriov-network-config-daemon pod become CrashLoopBackOff


Version-Release number of selected component (if applicable):
 Red Hat Enterprise Linux CoreOS 420.8.20190721.0 (Ootpa)

How reproducible:


Steps to Reproduce:
1. setup the sriov cluster 
2. install the sriov operator from web console
3. Create the SriovNetworkNodePolicy CR on xxv710 with following:
   
   apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
  creationTimestamp: '2019-07-30T08:28:20Z'
  generation: 4
  name: policy-1
  namespace: sriov-network-operator
  resourceVersion: '1994420'
  selfLink: >-
    /apis/sriovnetwork.openshift.io/v1/namespaces/sriov-network-operator/sriovnetworknodepolicies/policy-1
  uid: fd1f597a-b2a3-11e9-a8e4-2e808f6aa7e1
spec:
  deviceType: vfio-pci
  mtu: 1500
  nicSelector:
    pfNames:
      - ens1f0
    rootDevices:
      - '0000:3b:00.0'
    vendor: '8086'
  nodeSelector:
    feature.node.kubernetes.io/sriov-capable: 'true'
  numVfs: 6
  priority: 99
  resourceName: intelnics
**************
4. Check the config daemon pod become to Crash

Actual results:

logs:

E0730 08:31:11.652714   44720 utils.go:118] SyncNodeState(): fail to config sriov interface 0000:3b:00.0: write /sys/bus/pci/drivers/vfio-pci/bind: no such device


Expected results:

should work well

Additional info:

this issue happen on coreOS