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.

Description of problem:
There is no simple way of getting DBUS-PATH of a connection/device by name, one have to output all the connections/devices and then filter results. 

Version-Release number of selected component (if applicable):
NetworkManager-1.20.0-2.el8

How reproducible:
allways

Steps to Reproduce:
nmcli -g DBUS-PATH device show eth0
nmcli -g DBUS-PATH connection show id eth0

Actual results:
Error: 'device show': invalid field 'DBUS-PATH'; allowed fields: GENERAL,CAPABILITIES,WIFI-PROPERTIES,AP,WIRED-PROPERTIES,WIMAX-PROPERTIES,NSP,IP4,DHCP4,IP6,DHCP6,BOND,TEAM,BRIDGE,VLAN,BLUETOOTH,CONNECTIONS

Expected results:
DBUS-PATH should be returned

Additional info:
filtering the output of `nmcli -g DBUS-PATH,DEVICE device` is only option of getting DBUS-PATH, the same for connections

Created attachment 1609305 [details]
[PATCH] cli: expose device D-Bus path

The patch above exposes the device D-Bus path. For the connection it is a bit more complex because we currently show only properties from the profile itself, not metadata. Perhaps we could add a new 'CONNECTION' section that is not displayed by default but only when passing '-f all'...

(In reply to Beniamino Galvani from comment #2)
> Created attachment 1609305 [details]
> [PATCH] cli: expose device D-Bus path

lgtm. Merged to master and nm-1-22.

master:  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/622eef4882028fa49a1ffd836ffdb6c633863197
nm-1-22: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/d33bea21b73dc9d15dd08a05eb7c7dbd1f382a0e

moving bug back to NEW for other part of the feature (comment 3).

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.