diff options
| author | Fernando Fernandez Mancera <ffmancera@riseup.net> | 2021-11-23 11:31:40 +0100 |
|---|---|---|
| committer | Fernando Fernandez Mancera <ffmancera@riseup.net> | 2021-11-28 20:34:38 +0100 |
| commit | e44cdc79812d82dcf24e915f440497bc503bffe4 (patch) | |
| tree | 02c86974d1e587ed20251fece848da3ee1842b2b /src/core/ppp/nm-ppp-manager.c | |
| parent | 454999505241117b0ac293e426fc01dc76c6e70f (diff) | |
| download | NetworkManager-e44cdc79812d82dcf24e915f440497bc503bffe4.tar.gz | |
ovsdb: deactivate removed device if does not have a master
When using OVS link aggregation ports, NetworkManager ovsdb is removing
the ports when cleaning it up. If that happens, it should deactivate the
device even if it does not have controller or the state is not
assume/external.
An interface that is port of the OVS bonding can be activated before the
ovsdb clean up, if it is not deactivated then NetworkManager will finish
with a wrong configuration. The 'ovsdb_device_removed()' is already
checking that the device is "ovs-interface" with subtype "system".
Diffstat (limited to 'src/core/ppp/nm-ppp-manager.c')
0 files changed, 0 insertions, 0 deletions