Bug 1378794 - [nmcli] no longer able to set device managed and autoconnect
Summary: [nmcli] no longer able to set device managed and autoconnect
Keywords:
Status: CLOSED NOTABUG
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: Lubomir Rintel
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 09:38 UTC by Thomas Haller
Modified: 2016-09-23 09:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-23 09:45:52 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Thomas Haller 2016-09-23 09:38:41 UTC 
Regression.


$ nmcli device modify wlp3s0 managed yes
Error: invalid <setting>.<property> 'managed'.

also:

$ nmcli device modify wlp3s0 managed no
Error: Reading applied connection from device 'wlp3s0' (/org/freedesktop/NetworkManager/Devices/2) failed: Device is not activated



$ nmcli device modify wlp3s0 autoconnect yes
Connection successfully reapplied to device 'wlp3s0'.

^^ this is wrong too.
Comment 2 Thomas Haller 2016-09-23 09:45:52 UTC 
I mixed it up...


should be `nmcli device set $NAME managed`...

`nmcli device modify` does something different.


It seems ugly to me that we have "set" and "modify" sub-commands.
Note You need to log in before you can comment on or make changes to this bug.