SRIOV: During fuel deployment VF's are not enabled on a sriov enabled nic, when the nic supports less than 30 VF's
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel Contrail plugin |
Fix Released
|
High
|
Vitalii Kovalchuk |
Bug Description
Fuel-contrail-
contrail-build version: 3.0.2.0-
SRIOV was enabled through the Fuel GUI.
total number of VF's supported by the nic was 7.
root@node-1:~# cat /sys/class/
7
We saw that after deployment VF's were not enabled and required configuration to enable the SRIOV were not pushed to the server after the deployment.
interface did not list any VF's after the deployment.
# ip link show dev eno1
14: eno1: <BROADCAST,
link/ether 0c:c4:7a:a9:02:62 brd ff:ff:ff:ff:ff:ff
root@node-1:~# cat /sys/class/
0
root@node-1:~# ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
Loos like during the fuel provisioning by default it tries to enable 30 VF's on the nic with out checking the supported number of VF's.
Changed in fuel-plugin-contrail: | |
importance: | Undecided → High |
milestone: | none → 5.0.0 |
assignee: | nobody → Vitalii Kovalchuk (vkovalchuk) |
In plugin 5.0.0 plugin uses SR-IOV from Fuel, and it doesn't have this problem.