New bond does not activate as expected in certain scenario
Version 1.28.0-2+b1 from Debian Testing
When executing these commands:
# nmcli con mod cockpit1 connection.slave-type bond connection.master tbond
# nmcli con add connection.type bond connection.id tbond connection.interface-name tbond connection.autoconnect 1 connection.autoconnect-slaves 1 ethernet.cloned-mac-address $(cat /sys/class/net/cockpit1/address)
the new bond "tbond" does not fully activate and almost always does not get the configured MAC address:
# nmcli
cockpit1: connected to cockpit1
"cockpit1"
ethernet (veth), 5A:B4:D8:95:83:63, sw, mtu 1500
master tbond
route6 ff00::/8
tbond: connecting (getting IP configuration) to tbond
"tbond"
bond, B2:B5:B2:F4:94:C3, sw, mtu 1500
Sometimes it gets the configured MAC address, but still doesn't fully activate, and never receives a IP address.
This works as expected with version 1.26.4-1 from Fedora 33. "tbond" has the same MAC address as cockpit1 and activates fully, immediately receiving the same IP address as cockpit1 used to have.