Bug 2129952

Summary:	No setting for interface-name
Product:	Red Hat Enterprise Linux 9	Reporter:	Jim Wright <jim>
Component:	gnome-control-center	Assignee:	Felipe Borges <feborges>
gnome-control-center sub component:	Network and Wi-Fi panels	QA Contact:	Desktop QE <desktop-qa-list>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	cgarnach, jim, nm-team, tpopela
Version:	9.0	Keywords:	FutureFeature, MigratedToJIRA
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-15 19:34:24 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jim Wright 2022-09-26 19:14:41 UTC

Description of problem:
Desktop/Settings/Network, Profile Identity tab, the Name of the profile can be set, but there is no GUI setting to set the interface-name parameter, which would lock a profile to a given interface.  This apparently can only be set via the CLI.

Version-Release number of selected component (if applicable):
40.0-23.el9_0

How reproducible:
Very

Steps to Reproduce:
1. See above
2.
3.

Actual results:
Unable to change via GUI

Expected results:
Able to update via GUI

Additional info:
Ideally this should be a drop down menu of available interfaces.

Comment 1 Jim Wright 2022-09-29 19:43:57 UTC

Additional, not sure if this should be a separate enhancement request but it is related.

Currently RHEL writes out default profiles to /etc/NetworkManager/system-connections/ with the interface name as the file name for the connection profile, also populates this in the ID as well as interface-name fields.  Example:

[root@localhost system-connections]# ls
eno1.nmconnection  eno3.nmconnection  ens2f0np0.nmconnection
eno2.nmconnection  eno4.nmconnection  ens2f1np1.nmconnection
[root@localhost system-connections]# cat ens2f0np0.nmconnection
[connection]
id=ens2f0np0
uuid=8f93c397-3fec-42a4-a230-67dfa547c8fd
type=ethernet
autoconnect-retries=1
interface-name=ens2f0np0
timestamp=1657913326
zone=external

I see the value in having the profile name (Connection/ID above) be configurable, but once these files are initially created (including generic Profile 1 files), the file names do not change.  It seems that it would be allow for easier management for the file name to reflect the profile name, unless the interface-name is also set in which case the file name should be the iface name.

Comment 2 RHEL Program Management 2023-09-15 19:33:57 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-15 19:34:24 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.