Bug 1298580 - [REST] Attach network with boot protocol none via setupNetworks requires ip configuration details
Summary: [REST] Attach network with boot protocol none via setupNetworks requires ip c...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 3.6.2.5
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ovirt-3.6.3
: 3.6.3
Assignee: Alona Kaplan
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-14 13:31 UTC by Meni Yakove
Modified: 2016-02-18 11:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 11:17:25 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-3.6.z+
rule-engine: blocker+
ylavi: planning_ack+
danken: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 52650 0 master MERGED engine: Null ip configuration should be considered as NONE 2016-01-24 13:39:15 UTC
oVirt gerrit 52686 0 ovirt-engine-3.6 MERGED engine: Null ip configuration should be considered as NONE 2016-01-26 11:20:12 UTC
oVirt gerrit 52687 0 ovirt-engine-3.6.2 ABANDONED engine: Null ip configuration should be considered as NONE 2016-01-25 14:03:15 UTC

Description Meni Yakove 2016-01-14 13:31:08 UTC 
Description of problem:
Since rhevm-3.6.2.5-0.1 version attaching a network to host NIC via REST setupNetworks command requires boot protocol configuration even when the desired boot protocol is none.

Till now when no boot protocol was sent the default was none.
This breaks backward compatibility for existing scripts. 

Version-Release number of selected component (if applicable):
rhevm-3.6.2.5-0.1.el6.noarch


Steps to Reproduce:
1. Call setupNetworks via REST to attach network to host NIC without <ip_address_assignments>

Actual results:
The operation fails with error Network attachment of Network net1, Interface enp4s0f1 is missing IP configuration details.

Expected results:
Network is attached with boot protocol None
Comment 1 Dan Kenigsberg 2016-01-17 12:37:39 UTC 
This was the planned behaviour of the patches fixing bug 1270688.

We wanted to force the users of the API to state which IP config they would like to give to the network attachment.

Now that we realize that this has broken your scripts, we may reconsider.
Comment 2 Dan Kenigsberg 2016-01-20 09:07:58 UTC 
All right, let us induldge pm+qe.
Comment 3 Meni Yakove 2016-01-31 13:39:17 UTC 
rhevm-3.6.3-0.1.el6.noarch
Note You need to log in before you can comment on or make changes to this bug.