RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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.

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?

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.

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.