Skip to content

Commit

Permalink
Race in configure-ovs.sh affects bonding interface configuration.
Browse files Browse the repository at this point in the history
Bonded network configurations with mode=active-backup and
fail_over_mac=follow are not functioning due to a race when
activating network profiles. activate_nm_connections() attempts
to activate all its generated profiles that are not currently
in the "active" state. As autoconnect-slaves is set, once
br-ex is activated the bond and all its slaves are automatically
activated. Their state is set to "activating" until they become
active. The "activating" state is not tested for therefor some of
the subordinate profiles maybe activated multiple times causing a
race in the bonding driver and incorrectly configuring the bond.

Link: openshift#4605
Signed-off-by: David Wilder <[email protected]>
  • Loading branch information
DaveWilder committed Sep 23, 2024
1 parent a6ee4b4 commit 50817d1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion templates/common/_base/files/configure-ovs-network.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -573,7 +573,7 @@ contents:
# But set the entry in master_interfaces to true if this is a slave
# Also set autoconnect to yes
local active_state=$(nmcli -g GENERAL.STATE conn show "$conn")
if [ "$active_state" == "activated" ]; then
if [ "$active_state" == "activated" ] || [ "$active_state" == "activating" ]; then
echo "Connection $conn already activated"
if $is_slave; then
master_interfaces[$master_interface]=true
Expand Down

0 comments on commit 50817d1

Please sign in to comment.