Bug 1378794

Summary: [nmcli] no longer able to set device managed and autoconnect
Product: Red Hat Enterprise Linux 7 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED NOTABUG QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: atragler, bgalvani, lrintel, rkhan, thaller
Target Milestone: rc   
Target Release: ---   
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: 2016-09-23 09:45:52 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:

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.