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 2192859 - udev adds an unwanted altname to a renamed netdevice
Summary: udev adds an unwanted altname to a renamed netdevice
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: systemd
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: David Tardon
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-03 10:51 UTC by Michal Schmidt
Modified: 2024-01-20 04:25 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 12:33:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-plumbers systemd-rhel9 pull 191 0 None open (#2192859) Assign alternative names only on add uevent 2023-08-08 12:07:39 UTC
Github systemd systemd pull 25221 0 None Merged udev: set link alternative name if link is already up during rename 2023-08-08 11:56:20 UTC
Github systemd systemd pull 25980 0 None Merged udev,pid1: gracefully handle failure in renaming network interface 2023-08-08 11:56:20 UTC
Github systemd systemd pull 25986 0 None Merged test-netlink: cleanups 2023-08-17 14:33:33 UTC
Github systemd systemd pull 27655 0 None Merged udev/net: assign alternative names only on add event 2023-07-19 06:48:07 UTC
Red Hat Issue Tracker OCPBUGS-11281 0 None None None 2023-05-03 11:34:41 UTC
Red Hat Issue Tracker   RHEL-5988 0 None Migrated None 2023-09-21 12:32:27 UTC
Red Hat Issue Tracker RHELPLAN-156286 0 None None None 2023-05-03 10:51:55 UTC

Description Michal Schmidt 2023-05-03 10:51:25 UTC 
Description of problem:
In https://issues.redhat.com/browse/OCPBUGS-11281, it has been observed that when you rename a net device with 'ip link ... set name ...', the device's previous name becomes its altname. This causes a problem when you try to rename the device back and the existence of the altname prevents you. OCP ran into this issue.

Version-Release number of selected component (if applicable):
in RHEL 9.2: systemd-252-8.el9.x86_64
also in Fedora ELN: systemd-253.2-1.eln126.x86_64

How reproducible:
always

Steps to Reproduce:

[root@localhost ~]# ip link show enp1s0
2: enp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:a2:18:9e brd ff:ff:ff:ff:ff:ff
[root@localhost ~]# ip link set enp1s0 name foo
[root@localhost ~]# ip link show foo
2: foo: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:a2:18:9e brd ff:ff:ff:ff:ff:ff
    altname enp1s0

Actual results:
'foo' now has 'enp1s0' as its altname.

Expected results:
No new altname.

Additional info:
In RHEL 8, it behaves as expected.

Proposed fix for upstream: 
https://github.com/systemd/systemd/pull/27506
Comment 1 Sebastian Scheinkman 2023-05-22 12:11:25 UTC 
A different PR to handle this was merged https://github.com/systemd/systemd/pull/27655

Do you know when RHEL will be able to pick this one?
Comment 2 Michal Sekletar 2023-08-17 12:08:41 UTC 
(In reply to Sebastian Scheinkman from comment #1)
> A different PR to handle this was merged
> https://github.com/systemd/systemd/pull/27655
> 
> Do you know when RHEL will be able to pick this one?

We are going to address the issue in RHEL-9.3.
Comment 9 RHEL Program Management 2023-09-21 12:28:32 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 10 RHEL Program Management 2023-09-21 12:33:50 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.
Comment 11 Red Hat Bugzilla 2024-01-20 04:25:44 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.