Bug 1176391 - Adding host through REST API fails with cluster name but works with cluster ID
Summary: Adding host through REST API fails with cluster name but works with cluster ID
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-api
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6.0
Assignee: Eli Mesika
QA Contact: Karolína Hajná
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-21 08:55 UTC by Dima Kuznetsov
Modified: 2016-05-20 01:23 UTC (History)
8 users (show)

Fixed In Version: ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764
Clone Of:
Environment:
Last Closed: 2015-11-04 11:25:58 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)
A script that creates new dc/cluster and attempts to add a host. (1.19 KB, text/plain)
2014-12-21 08:55 UTC, Dima Kuznetsov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 36317 0 master MERGED core:fix adding host from REST API Never

Description Dima Kuznetsov 2014-12-21 08:55:38 UTC
Created attachment 971672 [details]
A script that creates new dc/cluster and attempts to add a host.

Description of problem:
When using the REST API (through python SDK in my case), adding host fails with the following error if cluster is specified by name.
status: 400
reason: Bad
detail: Cannot add Host. Cluster ID is not valid.

Version-Release number of selected component (if applicable):
master

How reproducible:
100%


Steps to Reproduce:
1. Bring up ovirt-engine
2. Change attached script to correct addresses and run it
3.

Actual results:
Adding host fails

Expected results:
Adding host succeeds

Additional info:
Works on 3.5 rpms, could be related to http://gerrit.ovirt.org/27578

Comment 1 Karolína Hajná 2015-04-27 11:47:55 UTC
Verified on oVirt 3.6.0-1

Comment 3 Sandro Bonazzola 2015-11-04 11:25:58 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.


Note You need to log in before you can comment on or make changes to this bug.