After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 706141 - nmcli waits forever when I remove connection
nmcli waits forever when I remove connection
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: nmcli
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-08-16 14:42 UTC by Jiri Pirko
Modified: 2013-09-09 16:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jiri Pirko 2013-08-16 14:42:31 UTC 
# sudo nmcli con add type bond
# sudo nmcli con
NAME          UUID                                  TYPE            TIMESTAMP-REAL                   
bond          b41bd73f-583b-449f-90ec-4eb60d52ede5  bond            never                            
System eth0x  5445eaf0-db79-ee09-647b-f4835548b263  802-3-ethernet  Fri 16 Aug 2013 04:37:12 PM CEST 
# sudo nmcli con add type bond-slave ifname e2 master b41bd73f-583b-449f-90ec-4eb60d52ede5
# sudo nmcli con
NAME           UUID                                  TYPE            TIMESTAMP-REAL                   
bond-slave-e2  41e467e2-4d98-42d2-9159-8cb8d77db1eb  802-3-ethernet  Fri 16 Aug 2013 04:37:36 PM CEST 
bond           b41bd73f-583b-449f-90ec-4eb60d52ede5  bond            Fri 16 Aug 2013 04:37:36 PM CEST 
System eth0x   5445eaf0-db79-ee09-647b-f4835548b263  802-3-ethernet  Fri 16 Aug 2013 04:37:12 PM CEST 
# sudo nmcli con delete 41e467e2-4d98-42d2-9159-8cb8d77db1eb
....WAITS FOREVER (or at least for a loooong time)....

The same happens when I remove bond master, bridge master, bridge slave, etc.


NM log:
NetworkManager[21529]: <info> (e2): device state change: activated -> disconnected (reason 'connection-removed') [100 30 38]
NetworkManager[21529]: <info> (e2): deactivating device (reason 'connection-removed') [38]
NetworkManager[21529]: <info> (e2): link disconnected
NetworkManager[21529]: <info> (nm-bond): link disconnected (deferring action for 4 seconds)
NetworkManager[21529]: <info> (nm-bond): released bond slave e2 (success 1)
NetworkManager[21529]: <info> (e2): bringing up device.
NetworkManager[21529]: <info> (e2): link connected
NetworkManager[21529]: <warn> Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details.
NetworkManager[21529]: <info> (e2): device state change: disconnected -> unavailable (reason 'carrier-changed') [30 20 40]
NetworkManager[21529]: <info> (e2): deactivating device (reason 'carrier-changed') [40]
NetworkManager[21529]: <info> (e2): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
NetworkManager[21529]: <info> (nm-bond): link disconnected (calling deferred action)
DHCPDISCOVER on nm-bond to 255.255.255.255 port 67 interval 17 (xid=0x21ce90f7)
NetworkManager[21529]: <warn> (nm-bond): DHCPv4 request timed out.
NetworkManager[21529]: <info> (nm-bond): canceled DHCP transaction, DHCP client pid 21563
NetworkManager[21529]: <info> Activation (nm-bond) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
NetworkManager[21529]: <info> Activation (nm-bond) Stage 4 of 5 (IPv4 Configure Timeout) started...
NetworkManager[21529]: <info> Activation (nm-bond) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Comment 1 Dan Winship 2013-09-09 13:29:02 UTC 
fixed in git