Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionMichal Sekletar
2022-03-10 15:14:55 UTC
Description of problem:
Our RHEL-8 kernel has support for setting alternative names for network interfaces, introduced in [1]. However, we are missing support for querying the information about the interface using its previously set alternative name. Hence, I'd like to request the backport of [2] which introduces this possibility.
Version-Release number of selected component (if applicable):
kernel-4.18.0-348.12.2.el8_5
How reproducible:
deterministic
Steps to Reproduce:
1. ip link add type dummy dummy0
2. ip link prop add dummy0 altname dum0
3. ip link prop add dummy0 altname longalternativeinterfacenameofdummy0
4. ip link show dum0
5. ip link show longalternativeinterfacenameofdummy0
Actual results:
ip link show dum0
4: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 66:3e:3b:58:90:66 brd ff:ff:ff:ff:ff:ff
ip link show longalternativeinterfacenameofdummy0
Device "longalternativeinterfacenameofdummy0" does not exist.
Expected results:
Using name "longalternativeinterfacenameofdummy0" should also be usable to query the information about the interface.
Additional info:
[1] https://github.com/torvalds/linux/commit/7a56493f0620cc1b4cffc9bc59289fdefe76b5f3
[2] https://github.com/torvalds/linux/commit/76c9ac0ee878f6693d398d3a95ccaf85e1f597a6
Checked the bug is fixed. Set TESTED.
[root@dell-per730-49 ~]# uname -r
4.18.0-396.g413c.el8.mr2584_220531_1211.x86_64
[root@dell-per730-49 ~]# ip link add type dummy dummy0
[root@dell-per730-49 ~]# ip link prop add dummy0 altname dum0
[root@dell-per730-49 ~]# ip link prop add dummy0 altname longalternativeinterfacenameofdummy0
[root@dell-per730-49 ~]# ip link show dum0
8: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether ce:7e:98:34:a4:0d brd ff:ff:ff:ff:ff:ff
altname dum0
altname longalternativeinterfacenameofdummy0
[root@dell-per730-49 ~]# ip link show longalternativeinterfacenameofdummy0
8: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether ce:7e:98:34:a4:0d brd ff:ff:ff:ff:ff:ff
altname dum0
altname longalternativeinterfacenameofdummy0
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: kernel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:7683
Description of problem: Our RHEL-8 kernel has support for setting alternative names for network interfaces, introduced in [1]. However, we are missing support for querying the information about the interface using its previously set alternative name. Hence, I'd like to request the backport of [2] which introduces this possibility. Version-Release number of selected component (if applicable): kernel-4.18.0-348.12.2.el8_5 How reproducible: deterministic Steps to Reproduce: 1. ip link add type dummy dummy0 2. ip link prop add dummy0 altname dum0 3. ip link prop add dummy0 altname longalternativeinterfacenameofdummy0 4. ip link show dum0 5. ip link show longalternativeinterfacenameofdummy0 Actual results: ip link show dum0 4: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 66:3e:3b:58:90:66 brd ff:ff:ff:ff:ff:ff ip link show longalternativeinterfacenameofdummy0 Device "longalternativeinterfacenameofdummy0" does not exist. Expected results: Using name "longalternativeinterfacenameofdummy0" should also be usable to query the information about the interface. Additional info: [1] https://github.com/torvalds/linux/commit/7a56493f0620cc1b4cffc9bc59289fdefe76b5f3 [2] https://github.com/torvalds/linux/commit/76c9ac0ee878f6693d398d3a95ccaf85e1f597a6