Bug 1460527 - Spurious device name in the output of nmcli device wifi subcommands
Summary: Spurious device name in the output of nmcli device wifi subcommands
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-11 21:01 UTC by Beniamino Galvani
Modified: 2017-08-01 09:30 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.8.0-8.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 09:30:33 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2299 normal SHIPPED_LIVE Moderate: NetworkManager and libnl3 security, bug fix and enhancement update 2017-08-01 12:40:28 UTC

Description Beniamino Galvani 2017-06-11 21:01:01 UTC
Description of problem:
When running one of:

  nmcli device wifi list ifname wlan0
  nmcli device wifi connect <SSID> ifname wlan0

nmcli wrongly adds the device name to the output. This can break scripts that parse the output of the above commands.


Version-Release number of selected component (if applicable):
1.8.0-6


How reproducible:
100%


Steps to Reproduce:

 # nmcli device wifi list ifname wlan0
 wlan0
 IN-USE  SSID    MODE   CHAN  RATE        SIGNAL  BARS  SECURITY
 *       aoeu    Infra  1     130 Mbit/s  90      ▂▄▆█  WPA2


 # nmcli device wifi connect ssid ifname wlan0
 wlan0
 Device 'wlan0' successfully activated with '77d008bf-6a7b-40bf-a30c-cec6f0d16a36'.


Expected results:
The 'wlan0' line shouldn't be there.


Additional info:
Fixed upstream by https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d2b4332b36686dd5d7382d996743f0ffa1a0fdda

Comment 3 errata-xmlrpc 2017-08-01 09:30:33 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, 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-2017:2299


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