Created attachment 1739861 [details]
ovs-vswitchd logs

Description of problem:
When enable the feature ovs-hw-offload, the worker will cannot access the kube api (172.30.0.1:443)

Version-Release number of selected component (if applicable):
4.7.0-0.nightly-2020-12-14-165231
sriov-network-operator.4.7.0-202012161545.p0

How reproducible:
always

Steps to Reproduce:
1. Setup the baremetal cluster and make the Mallanox cx5 card nic as the default network api
2. install 4.7 sriov operator
3. Enable the ovs-hw-offload feature by
oc patch -n openshift-sriov-network-operator sriovoperatorconfigs.sriovnetwork.openshift.io default --type='merge' --patch '{"spec":{"enableOvsOffload":true}}'
4. Create the following policy

piVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
  name: policy-mlx
  namespace: openshift-sriov-network-operator
spec:
  deviceType: netdevice
  mtu: 1500
  nicSelector:
    deviceID: "1017"
    rootDevices:
    - 0000:b0:00.0
    vendor: "15b3"
    pfNames:
    - ens801f0
  nodeSelector:
    feature.node.kubernetes.io/network-sriov.capable: "true"
  eSwitchMode: "switchdev"
  numVfs: 4
  priority: 5
  resourceName: mlxnics

5. check the node will be always scheduledisable and node cannot be accessed to 172.30.0.1:443
6. Check the ovs-vswitch logs 

Actual results:

please see the attachment for ovs-vswitch logs

Expected results:


Additional info: