Bug 1991493
| Summary: | SriovNetworkNodePolicy failed to enable VFs on PF after upgrade | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ying Wang <yingwang> |
| Component: | Networking | Assignee: | zenghui.shi <zshi> |
| Networking sub component: | SR-IOV | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED DUPLICATE | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | zzhao |
| Version: | 4.9 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-08-19 09:02:45 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: | |||
Hi Wang Ying, what is the pci address of device ens2f0? # ethtool -i ens2f0 Thanks! Zenghui (In reply to zenghui.shi from comment #3) > Hi Wang Ying, > > what is the pci address of device ens2f0? > > # ethtool -i ens2f0 > > Thanks! > Zenghui # ethtool -i ens2f0 driver: mlx5_core version: 5.0-0 firmware-version: 14.23.1020 (MT_2420110034) expansion-rom-version: bus-info: 0000:5f:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes @zenghui, this issue like upgrade issue I met last time when sriov operator upgrade from 4.8 to 4.9 this issue should be caused by the serviceaccount did not exist for sriov-config-daemon. So close this bug as duplicated now with https://bugzilla.redhat.com/show_bug.cgi?id=1994434 *** This bug has been marked as a duplicate of bug 1994434 *** |
Description of problem: Applying a SriovNetworkNodePolicy to create VFs, the policy can be created successfully but VFs are not enabled. Version-Release number of selected component (if applicable): 4.9 How reproducible: Always Steps to Reproduce: 1. Creating policy to enable VFs on PF ens2f0 [root@dell-per740-36 yingwang]# cat mlx277netpolicy.yaml apiVersion: sriovnetwork.openshift.io/v1 kind: SriovNetworkNodePolicy metadata: name: mlx277netpolicy namespace: openshift-sriov-network-operator spec: mtu: 1800 nicSelector: deviceID: '1015' pfNames: - ens2f0 vendor: '15b3' nodeSelector: feature.node.kubernetes.io/sriov-capable: 'true' numVfs: 10 resourceName: mlx277netpolicy [root@dell-per740-36 yingwang]# oc create -f mlx277netpolicy.yaml sriovnetworknodepolicy.sriovnetwork.openshift.io/mlx277netpolicy created 2. Check ens2f0 but no VFs are enabled sh-4.4# ip -d link show ens2f0 10: ens2f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 98:03:9b:48:dd:98 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 9978 addrgenmode none numtxqueues 256 numrxqueues 64 gso_max_size 65536 gso_max_segs 65535 sh-4.4# Actual results: VFs are not enabled Expected results: VFs should be enabled after creating sriovnetworknodepolicy Additional info: [root@dell-per740-36 yingwang]# oc version Client Version: 4.8.0-0.nightly-2021-04-23-131610 Server Version: 4.9.0-0.nightly-2021-08-06-060446 Kubernetes Version: v1.21.1+8268f88 [root@dell-per740-36 yingwang]# oc get csv -n openshift-sriov-network-operator NAME DISPLAY VERSION REPLACES PHASE sriov-network-operator.4.9.0-202108060405 SR-IOV Network Operator 4.9.0-202108060405 sriov-network-operator.4.8.0-202108041625 Succeeded