Bug 1781718

Summary: [sriov] The exist VF disappeared when worker reboot
Product: OpenShift Container Platform Reporter: zhaozhanqi <zzhao>
Component: NetworkingAssignee: Peng Liu <pliu>
Networking sub component: SR-IOV QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: high CC: pliu, zshi
Version: 4.3.0Flags: pliu: needinfo-
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1782147 (view as bug list) Environment:
Last Closed: 2020-05-04 11:19:30 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: 1782147    

Description zhaozhanqi 2019-12-10 13:28:37 UTC
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

Comment 4 Peng Liu 2019-12-11 09:32:27 UTC
PR https://github.com/openshift/sriov-network-operator/pull/136 merged

Comment 6 zhaozhanqi 2019-12-16 02:39:50 UTC
Verified this bug, the Vf can work well when the worker reboot

Comment 8 errata-xmlrpc 2020-05-04 11:19:30 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:0581