Bug 1745574

Summary: [RFE] nmcli not showing DBUS-PATH of particular device/connection
Product: Red Hat Enterprise Linux 8 Reporter: Filip Pokryvka <fpokryvk>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: acardace, atragler, bgalvani, fgiudici, lmiksik, lrintel, rkhan, sukulkar, thaller
Target Milestone: rcKeywords: FutureFeature, RFE, Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-26 07:30:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
[PATCH] cli: expose device D-Bus path none

Description Filip Pokryvka 2019-08-26 11:49:20 UTC 
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
Comment 2 Beniamino Galvani 2019-08-29 08:59:35 UTC 
Created attachment 1609305 [details]
[PATCH] cli: expose device D-Bus path
Comment 3 Beniamino Galvani 2019-08-29 09:01:48 UTC 
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'...
Comment 4 Thomas Haller 2019-12-10 16:59:13 UTC 
(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.
Comment 5 Thomas Haller 2019-12-10 17:00:21 UTC 
master:  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/622eef4882028fa49a1ffd836ffdb6c633863197
nm-1-22: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/d33bea21b73dc9d15dd08a05eb7c7dbd1f382a0e
Comment 6 Thomas Haller 2019-12-10 17:00:56 UTC 
moving bug back to NEW for other part of the feature (comment 3).
Comment 13 RHEL Program Management 2021-02-26 07:30:48 UTC 
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.