Bug 1340862 - Can not create Openstack network provider in rest v3
Summary: Can not create Openstack network provider in rest v3
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Marcin Mirecki
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-30 12:56 UTC by Marcin Mirecki
Modified: 2016-07-05 07:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Rest API v3 calls to network provider create will automatically create a provider of type OPENSTACK_NETWORK. Since v4, it is possible to create either an openstack or external provider.
Clone Of:
Environment:
Last Closed: 2016-07-05 07:42:44 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.0.0+
rule-engine: blocker+
rule-engine: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 58266 0 master MERGED restapi: Adding 'type' to openstacknetworkprovider v3 in adapter 2016-06-01 12:47:25 UTC
oVirt gerrit 58679 0 ovirt-engine-4.0 MERGED restapi: Adding 'type' to openstacknetworkprovider v3 in adapter 2016-06-06 21:19:56 UTC

Description Marcin Mirecki 2016-05-30 12:56:58 UTC 
An openstack network provider can not be created using rest api v3.

The problem is the type property which has been added. It is not present in v3, and must be added the v3 adapter.
Comment 1 Red Hat Bugzilla Rules Engine 2016-05-30 15:15:06 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 2 Meni Yakove 2016-06-22 08:22:32 UTC 
rhevm-4.0.0.5-0.1.el7ev.noarch
Comment 3 Sandro Bonazzola 2016-07-05 07:42:44 UTC 
oVirt 4.0.0 has been released, closing current release.
Note You need to log in before you can comment on or make changes to this bug.