This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2129952 - No setting for interface-name
Summary: No setting for interface-name
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome-control-center
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Felipe Borges
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-26 19:14 UTC by Jim Wright
Modified: 2023-09-15 19:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-15 19:34:24 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4210 0 None Migrated None 2023-09-15 19:34:16 UTC
Red Hat Issue Tracker RHELPLAN-134930 0 None None None 2022-09-26 19:27:53 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.