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 743187 - [review PATCH] cli: try to reactivate connections on the same device
[review PATCH] cli: try to reactivate connections on the same device
Status: RESOLVED DUPLICATE of bug 730492
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-01-19 15:37 UTC by Lubomir Rintel
Modified: 2015-02-28 15:03 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
cli: try to reactivate connections on the same device (2.32 KB, text/plain)
2015-01-19 15:37 UTC, Lubomir Rintel 		Details

Description Lubomir Rintel 2015-01-19 15:37:11 UTC 
Created attachment 294895 [details]
cli: try to reactivate connections on the same device

If we reactivate an active connection that is valid for multiple devices, try
pick the device that the device is already using. This avoids failing with
"Connection '...' is already active on ..." while choosing a different device.

https://bugzilla.redhat.com/show_bug.cgi?id=1182085
Comment 1 Thomas Haller 2015-01-19 16:09:54 UTC 
IMO, this review patch tries to fix bug 730492.

But I don't think that nmcli should try to determine the interface. It should not specify the interface and NM should instead do the right thing.
Comment 2 Lubomir Rintel 2015-02-07 16:43:43 UTC 

*** This bug has been marked as a duplicate of bug 730492 ***
Comment 3 Dan Williams 2015-02-28 15:03:31 UTC 
Yeah, we should just change the NM behavior.  If the client wants a specific interface, then they can specify that, but I think right now the choice in NM is not deterministic.