Bug 1367737

Summary: nmcli asks for ipv4 and ipv6 method even if these were specified
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 7.3CC: aloughla, 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-11-03 19:28:37 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 Vladimir Benes 2016-08-17 10:50:11 UTC 
Description of problem:
[root@qe-dell-ovs5-vm-56 ~]# nmcli  connection add type bond ipv4.method manual ipv4.addresses 1.1.1.1/24 ipv6.method manual ipv6.addresses 1::2/128
Do you also want to set 'ipv4.method' to 'manual'? [yes]: 
Do you also want to set 'ipv6.method' to 'manual'? [yes]: 
Connection 'bond' (463acf4f-8b87-476c-9f79-e92203175674) successfully added.


Version-Release number of selected component (if applicable):
NetworkManager-1.4.0-0.5.beta1.el7.x86_64
Comment 1 Thomas Haller 2016-08-20 07:59:22 UTC 
it anyway seems wrong to ask at all, given that no --ask is provided.

This seems like a major regression. Over to Lubormir :)
Comment 2 Thomas Haller 2016-08-24 15:43:56 UTC 
fixed upstream by lrintel:

master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=79c81bbb8cf5903462caf9f60e1bca4a22f3280f

nm-1-4: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=afab2b8112f686b47ba2ed279fad767645b40214
Comment 4 Vladimir Benes 2016-08-26 19:40:35 UTC 
connection is created w/o any further questions
Comment 6 errata-xmlrpc 2016-11-03 19:28:37 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://rhn.redhat.com/errata/RHSA-2016-2581.html