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 1673321 - [RFE] Allow to match network devices by PCI Address
Summary: [RFE] Allow to match network devices by PCI Address
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1695634 1723391 1807630
TreeView+ depends on / blocked
 
Reported: 2019-02-07 11:29 UTC by Till Maas
Modified: 2020-11-04 01:49 UTC (History)
10 users (show)

Fixed In Version: NetworkManager-1.26.0-0.1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1723391 (view as bug list)
Environment:
Last Closed: 2020-11-04 01:48:18 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4499 0 None None None 2020-11-04 01:49:06 UTC

Description Till Maas 2019-02-07 11:29:40 UTC
Description of problem:
Currently, NetworkManager only allows to specify devices by name or MAC address. Since the device name is not stable and the MAC address requires an inventory about which MAC addresses are used, it would be nice to be able to specify a network card by PCI address, i.e. 0000:00:1f.6.

Additional info:
This could be implemented by a match setting that already exists for interface-name but not yet for PCI ID.

Comment 1 Thomas Haller 2019-02-07 11:38:10 UTC
do you know how to obtain the PCI address?

Comment 2 Thomas Haller 2019-02-07 11:56:43 UTC
there is:

 - grep PCI_SLOT_NAME /sys/class/net/*/device/uevent

 - ethtool -i eth0
 
     - which uses ETHTOOL_GDRVINFO and "struct ethtool_drvinfo"

 - udevadm info -a -p /sys/class/net/eth0

 - sudo lshw -c network -businfo  

 - lspci -D 

 - udevadm info /sys/class/net/eth0 



Note in `man systemd.link` there is:

       Path=
           A whitespace-separated list of shell-style globs matching the persistent path, as exposed by the udev property "ID_PATH".


and 

  $ udevadm info /sys/class/net/eth0 | grep ID_PATH=



So, we probably want to implement this udev "path".

Comment 9 Beniamino Galvani 2020-06-10 15:37:53 UTC
Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/536

Comment 16 errata-xmlrpc 2020-11-04 01:48:18 UTC
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 (NetworkManager 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/RHBA-2020:4499


Note You need to log in before you can comment on or make changes to this bug.