-
Lubomir Rintel authored
If we surprise-remove the master, slaves would immediately attempt to bring things up by autoconnecting. Not cool. Policy, however, blocks autoconnect if the slaves disconnect due to "dependency-failed", and it indeed seems to be an appropriate reason here: $ nmcli c add type bridge $ nmcli c add type dummy ifname dummy0 master bridge autoconnect yes $ nmcli c del bridge $ Before: (nm-bridge): state change: ip-config -> deactivating (reason 'connection-removed') (nm-bridge): state change: deactivating -> disconnected (reason 'connection-removed') (nm-bridge): detached bridge port dummy0 (dummy0): state change: activated -> disconnected (reason 'connection-removed') (nm-bridge): state change: disconnected -> unmanaged (reason 'user-requested') (dummy0): state change: disconnected -> unmanaged (reason 'user-requested') policy: auto-activating connection 'bridge-slave-dummy0' After: (nm-bridge): state change: ip-config -> deactivating (reason 'connection-removed') (nm-bridge): state change: deactivating -> disconnected (reason 'connection-removed') (nm-bridge): detached bridge port dummy0 (dummy0): state change: activated -> deactivating (reason 'dependency-failed') (nm-bridge): state change: disconnected -> unmanaged (reason 'user-requested') (dummy0): state change: deactivating -> disconnected (reason 'dependency-failed') (dummy0): state change: disconnected -> unmanaged (reason 'user-requested') https://github.com/NetworkManager/NetworkManager/pull/319 (cherry picked from commit 8f2a8a52)
b4359e57