VF-lag failed to activate in Nvidia\Mellanox Nics at deployment stage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-net-config |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description of problem:
Provisioned the following config
- type: ovs_bridge
name: br-link0
mtu: 9000
use_dhcp: false
members:
- type: linux_bond
name: mx-bond
mtu: 9000
bonding_
members:
- type: sriov_pf
name: nic11
numvfs: 10
primary: true
promisc: true
use_dhcp: false
defroute: false
link_mode: switchdev
- type: sriov_pf
name: nic12
numvfs: 10
promisc: true
use_dhcp: false
defroute: false
link_mode: switchdev
- type: vlan
device: mx-bond
vlan_id: {{ lookup('vars', networks_
addresses:
- ip_netmask: {{ lookup('vars', networks_
nic11 and nic12 are mellanox nics
After provisioning the above configuration, we'll see that VF-LAG functionality is broken with the following error message:
[ 1005.396799] mlx5_core 0000:03:00.0: mlx5_cmd_
[ 1005.411593] mlx5_core 0000:03:00.0: mlx5_create_
[ 1005.420340] mlx5_core 0000:03:00.0: mlx5_activate_
Make sure all VFs are unbound prior to VF LAG activation or deactivation
And also, it may break the connectivity over the vlan interface.
summary: |
- VF-lag failed to activate in Nvidia\Mellanox Nics at deployment sate + VF-lag failed to activate in Nvidia\Mellanox Nics at deployment stage |
Fix proposed to branch: master /review. opendev. org/c/openstack /os-net- config/ +/883503
Review: https:/