-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.16
-
None
-
None
-
2
-
False
-
When we install the SRIOV operator on a SuperMicro ARM server with a BF3 NIC, the node enters a reboot loop and only exits the reboot loop if we remove the SriovOperatorConfig and SriovNetworkNodePolicy.
Steps to reproduce:
- Install the SRIOV operator.
- Add an SriovNetworkNodePolicy targetting the BF3 NIC
Here is my SriovNetworkNodePolicy
apiVersion: sriovnetwork.openshift.io/v1 kind: SriovNetworkNodePolicy metadata: name: sriov-nnp-du-mh namespace: openshift-sriov-network-operator spec: deviceType: netdevice isRdma: true nicSelector: pfNames: - enP2s2f1np1 nodeSelector: node-role.kubernetes.io/master: "" numVfs: 4 priority: 10 resourceName: du_mh