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-30 12:17:44 UTC
Description of problem:
In net_id we are now trying to avoid naming conflict for network devices which have PCI hotplug slot associated with the parent PCI bridge. This was introduced in, https://github.com/systemd/systemd/commit/2c8ec0095e6fd2e72879d4915ff8a9e5c0664d0b and it is correct behaviour for devices which share single PCI function. However, for multifunction devices it is not necessary to avoid slot based naming because there won't be any conflict to begin as function number will be appended after slot number and resulting interface names will be e.g. ens1f1, ens1f2.
Version-Release number of selected component (if applicable):
systemd-250-5.el9_0
How reproducible:
deterministic
Steps to Reproduce:
1. Boot RHEL-9 on system which has multiport, multifunction NIC installed in PCI-e hotplug slot (i.e. not integrated on the motherboard).
Actual results:
Interface names assigned to the interfaces will be based on PCI topology, e.g. enp59s0f0np0 enp59s0f1np1.
Expected results:
Slot based names are used if possible, e.g. ens1f0np0, ens1f1np1.
Additional info:
https://github.com/systemd/systemd/pull/22844
System which can be used for testing is dell-per740-06.rhts.eng.pek2.redhat.com.
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 (new packages: systemd), 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/RHBA-2022:3979