Fix breaking vf-lag functionality in os-net-config
Because of racing issue to activate vf-lag after moving the second
sriov_pf interface to switchdev mode in Nvidia\Mellanox nics, we may
bind sriov_vfs while the LAG is not active yet.
Another reason for breaking vf-lag functionality is that we are doing
ifdown/ifup for sriov_pfs after binding the vfs(in case of linux_bond
is member of ovs_bridge).
As a solution for this issue, we are doing the binding after assuring
the LAG is active, and also moving the ifdown/ifup before start binding
Closes-Bug: #2020085
Change-Id: If0cad8c856ee62064205b9a88f0148980653fcb2
(cherry picked from commit b1a7c9c5f0c2832ff504ea4557305ca1b94a196e)
Reviewed: https:/ /review. opendev. org/c/openstack /os-net- config/ +/884747 /opendev. org/openstack/ os-net- config/ commit/ de876c5f8f91bff a1a30e9f27929bf 30b7836e2a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/wallaby
commit de876c5f8f91bff a1a30e9f27929bf 30b7836e2a
Author: waleedm <email address hidden>
Date: Thu May 18 12:54:29 2023 +0000
Fix breaking vf-lag functionality in os-net-config
Because of racing issue to activate vf-lag after moving the second
sriov_pf interface to switchdev mode in Nvidia\Mellanox nics, we may
bind sriov_vfs while the LAG is not active yet.
Another reason for breaking vf-lag functionality is that we are doing
ifdown/ifup for sriov_pfs after binding the vfs(in case of linux_bond
is member of ovs_bridge).
As a solution for this issue, we are doing the binding after assuring
the LAG is active, and also moving the ifdown/ifup before start binding
Closes-Bug: #2020085 064205b9a88f014 8980653fcb2 ff504ea4557305c a1b94a196e)
Change-Id: If0cad8c856ee62
(cherry picked from commit b1a7c9c5f0c2832