Bug 1802936

Summary: The 'vfRange' in NodeState is incorrect when 'pfName' is not specified in node policy CR
Product: OpenShift Container Platform Reporter: Peng Liu <pliu>
Component: NetworkingAssignee: Peng Liu <pliu>
Networking sub component: SR-IOV QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: unspecified    
Version: 4.4   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1804986 (view as bug list) Environment:
Last Closed: 2020-05-04 11:36:41 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: 1804986    

Description Peng Liu 2020-02-14 07:16:03 UTC 
Description of problem:
The 'vfRange' in NodeState is incorrect when 'pfName' is not specified in node policy CR.
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. launch the operator, and apply the following node policy.
```
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
  name: policy-net-2
spec:
  resourceName: nic2
  nodeSelector:
    feature.node.kubernetes.io/network-sriov.capable: "true"
  priority: 99
  mtu: 9000
  numVfs: 4
  nicSelector:
    vendor: "8086"
    rootDevices: ['0000:86:00.1']
```

2. Check the node state of the worker node.
```
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodeState
metadata:
...
  name: nfvpe-25.oot.lab.eng.bos.redhat.com
  namespace: openshift-sriov-network-operator
...
spec:
  dpConfigVersion: "4454192"
  interfaces:
  - mtu: 9000
    name: ens803f1
    numVfs: 4
    pciAddress: 0000:86:00.1
    vfGroups:
    - deviceType: netdevice
      resourceName: nic2
      vfRange: 0-0
```

3.

Actual results:

The 'vfRange' was '0-0'.

Expected results:

The 'vfRange' should be '0-3'.

Additional info:
Comment 3 zhaozhanqi 2020-02-25 07:08:20 UTC 
Verified this bug see steps with https://bugzilla.redhat.com/show_bug.cgi?id=1804986#c4
Comment 5 errata-xmlrpc 2020-05-04 11:36:41 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