Bug 1369091

Summary:	[RFE] [nmtui] Add option to edit/modify an existing interface connection as a slave-bond
Product:	Red Hat Enterprise Linux 7	Reporter:	Michael Burman <mburman>
Component:	NetworkManager	Assignee:	Thomas Haller <thaller>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	aloughla, atragler, bgalvani, danken, lrintel, rkhan, sukulkar, thaller, ylavi
Target Milestone:	rc	Keywords:	FutureFeature, Improvement
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-02 09:19:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michael Burman 2016-08-22 13:17:32 UTC

Description of problem:
[RFE]-[nmtui] - Add option to edit/modify an existing interface connection as a slave-bond.

Currently on nmtui NM there is no option to modify an existing connection to be a slave-bond, but with nmcli we have an option to modify an existing connection.
If we would like to use an existing connection as a slave-bond for example, we will need to remove the exciting connections and add them as slave-bond.

I think it can be very useful to have sucj option via nmtui, this apply not only to modify to slave-bond, but to slave-team and bridge-team. 

Version-Release number of selected component (if applicable):
NetworkManager-1.0.6-30.el7_2.x86_64
rhel 7.2

How reproducible:
100

Steps to Reproduce:
1. Try to modify an existing connection to be a slave-bond

Actual results:
Not possible via nmtui
Possible via nmcli

Comment 2 Lubomir Rintel 2016-11-22 16:16:18 UTC

I'd be interested to hear what what is the exact use case here?

It seems somewhat difficult to me to design the UI in a way it wouldn't be too confusing.

Comment 3 Michael Burman 2016-11-23 09:26:57 UTC

Hi Lubomir, 

The exact use case is to be able to modify an existing and active connection as a slave-bond, slave-team, bridge-team and so on..without removing them and re-adding them back as slaves-* 
It is something that supported via nmcli or via ifcfg-* files configuration.

Yaniv, Dan, any input from you guys?

Comment 4 Dan Kenigsberg 2016-11-23 11:14:11 UTC

The original motivation was to keep an existing connection, to avoid proliferation of confusing connections.

Now that Vdsm can handle multiple connections, we don't really need this ourselves. Michael, thanks for opening it. Lubomir, thanks for reviewing it. But in RHV PoV it can be closed|wontfix.

Comment 5 Thomas Haller 2017-03-02 09:19:53 UTC

From how the nmtui UI works (that is, showing the slaves nested inside the masters connection), it doesn't fit well to be able to make a slave-connection a non-slave and vice-versa.

Similarly, you cannot use nmtui to change the device type of a connection.


Both of this is possible with nmcli, as nmcli allows to mutate all settings.


With comment 4, closing as WONTFIX.