Bug 1914065 - [sriov] config daemon did not trigger the ovs HW offload policy
Summary: [sriov] config daemon did not trigger the ovs HW offload policy
Keywords:
Status: CLOSED DUPLICATE of bug 1908570
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.8.0
Assignee: zenghui.shi
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-08 04:04 UTC by zhaozhanqi
Modified: 2021-01-19 02:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-19 02:14:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
configdaemon logs (377.86 KB, text/plain)
2021-01-08 04:04 UTC, zhaozhanqi
no flags Details

Description zhaozhanqi 2021-01-08 04:04:23 UTC
Created attachment 1745484 [details]
configdaemon logs

Description of problem:
Apply ovs HW offload policy. found VF cannot be inited. 

Version-Release number of selected component (if applicable):
4.7.0-202101051754.p0

How reproducible:


Steps to Reproduce:
1. setup cluster with mellanox card nic as the default network interface
2. install sriov operator
3. apply the following sriov policy
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
  name: policy-mlx-0
  namespace: openshift-sriov-network-operator
spec:
  deviceType: netdevice
  mtu: 1500
  nicSelector:
    deviceID: "1017"
    rootDevices:
    - 0000:b0:00.1
    vendor: "15b3"
    pfNames:
    - ens801f1
  nodeSelector:
    feature.node.kubernetes.io/network-sriov.capable0: "true"
  eSwitchMode: "switchdev"
  numVfs: 3
  priority: 6
  resourceName: mlxnics0

4. Check the status of sriovnetworknodestate
oc get sriovnetworknodestate  sriov-worker-0 -o yaml -n openshift-sriov-network-operator

5. check the logs of config daemon

Actual results:
step 4. the vf did not be inited.

apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodeState
metadata:
  creationTimestamp: "2021-01-06T09:27:04Z"
  generation: 21
  managedFields:
  - apiVersion: sriovnetwork.openshift.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:ownerReferences:
          .: {}
          k:{"uid":"d3e163d0-e5ee-4d92-b28b-9cb9048b11a8"}:
            .: {}
            f:apiVersion: {}
            f:blockOwnerDeletion: {}
            f:controller: {}
            f:kind: {}
            f:name: {}
            f:uid: {}
      f:spec:
        .: {}
        f:dpConfigVersion: {}
        f:interfaces: {}
    manager: sriov-network-operator
    operation: Update
    time: "2021-01-07T13:00:41Z"
  - apiVersion: sriovnetwork.openshift.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        .: {}
        f:interfaces: {}
        f:syncStatus: {}
    manager: sriov-network-config-daemon
    operation: Update
    time: "2021-01-07T13:05:38Z"
  name: sriov-worker-0
  namespace: openshift-sriov-network-operator
  ownerReferences:
  - apiVersion: sriovnetwork.openshift.io/v1
    blockOwnerDeletion: true
    controller: true
    kind: SriovNetworkNodePolicy
    name: default
    uid: d3e163d0-e5ee-4d92-b28b-9cb9048b11a8
  resourceVersion: "615829"
  uid: 79784269-3297-4f5d-bf9a-72e67ec434d2
spec:
  dpConfigVersion: "611930"
  interfaces:
  - eSwitchMode: switchdev
    linkType: eth
    mtu: 1500
    name: ens801f1
    numVfs: 3
    pciAddress: 0000:b0:00.1
    vfGroups:
    - deviceType: netdevice
      policyName: policy-mlx-0
      resourceName: mlxnics0
      vfRange: 0-2
status:
  interfaces:
  - deviceID: 37d2
    driver: i40e
    linkSpeed: 1000 Mb/s
    linkType: ETH
    mac: a4:bf:01:51:7e:3f
    mtu: 1500
    name: eno1
    pciAddress: 0000:3d:00.0
    totalvfs: 32
    vendor: "8086"
  - deviceID: 37d2
    driver: i40e
    linkSpeed: 1000 Mb/s
    linkType: ETH
    mac: a4:bf:01:51:7e:40
    mtu: 1500
    name: eno2
    pciAddress: 0000:3d:00.1
    totalvfs: 32
    vendor: "8086"
  - deviceID: 158b
    driver: i40e
    linkSpeed: -1 Mb/s
    linkType: ETH
    mac: 3c:fd:fe:ba:0a:78
    mtu: 1500
    name: ens803f0
    pciAddress: 0000:86:00.0
    totalvfs: 64
    vendor: "8086"
  - deviceID: 158b
    driver: i40e
    linkSpeed: 25000 Mb/s
    linkType: ETH
    mac: 3c:fd:fe:ba:0a:79
    mtu: 1500
    name: ens803f1
    pciAddress: 0000:86:00.1
    totalvfs: 64
    vendor: "8086"
  - deviceID: "1003"
    driver: mlx4_core
    linkSpeed: -1 Mb/s
    linkType: ETH
    mac: 00:02:c9:21:a3:a1
    mtu: 1500
    name: ens787
    pciAddress: 0000:88:00.0
    totalvfs: 8
    vendor: 15b3
  - deviceID: "1015"
    driver: mlx5_core
    linkSpeed: 25000 Mb/s
    linkType: ETH
    mac: 98:03:9b:a0:6e:1e
    mtu: 1500
    name: ens802f0
    pciAddress: 0000:af:00.0
    vendor: 15b3
  - deviceID: "1015"
    driver: mlx5_core
    linkSpeed: -1 Mb/s
    linkType: ETH
    mac: 98:03:9b:a0:6e:1f
    mtu: 1500
    name: ens802f1
    pciAddress: 0000:af:00.1
    vendor: 15b3
  - deviceID: "1017"
    driver: mlx5_core
    linkSpeed: 100000 Mb/s
    linkType: ETH
    mac: 98:03:9b:97:38:de
    mtu: 1500
    name: ens801f0
    pciAddress: 0000:b0:00.0
    totalvfs: 3
    vendor: 15b3
  - deviceID: "1017"
    driver: mlx5_core
    linkSpeed: 100000 Mb/s
    linkType: ETH
    mac: 98:03:9b:97:38:df
    mtu: 1500
    name: ens801f1
    pciAddress: 0000:b0:00.1
    totalvfs: 3
    vendor: 15b3
  syncStatus: Succeeded


Expected results:


Additional info:


Note You need to log in before you can comment on or make changes to this bug.