Bug 786886 - [ovirt] [engine-api] cancel-migrate: action is not supported
Summary: [ovirt] [engine-api] cancel-migrate: action is not supported
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.1
Assignee: Shahar Havivi
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-02 16:46 UTC by Haim
Modified: 2014-01-13 00:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 07:56:43 UTC
oVirt Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Haim 2012-02-02 16:46:00 UTC 
Description of problem:

using REST-API (same results with python SDK, trying to cancel migration, I get the following ERROR:

status: 400
reason: Bad Request
detail: [The Action ${action} is not supported for this Cluster or Data Center compatibility version]

2012-02-02 11:14:31,821 WARN  [org.ovirt.engine.core.bll.CancelMigrateVmCommand] (http--0.0.0.0-8080-5) CanDoAction of action CancelMigrateVm failed. Reasons:ACTION_NOT_SUPPORTED_FOR_CLUSTER_POOL_LEVEL

tried with both REST-API using poster and also using python SDK.


commit b266dd1e58c65497c8578495fb1cb32fbba92a65
Comment 1 Itamar Heim 2012-02-03 11:15:52 UTC 
actually, this action should only be supported on a > 3.0 cluster level.
(not sure that is indeed the validation).
need to create this cluster/dc level...
Comment 2 Shahar Havivi 2012-02-03 14:55:58 UTC 
Haim, what cluster version did you use?
Comment 3 Haim 2012-02-03 15:32:06 UTC 
(In reply to comment #2)
> Haim, what cluster version did you use?

I'm using 3.0 cluster. Didn't pass it in my commands though. Action is a part of vm sub collection, so should I ? How's the validation performed ?
Comment 4 Shahar Havivi 2012-02-03 16:47:03 UTC 
well it should only work for 3.2 cluster,
if you don't have that in the UI, you may need to add that to the DB
Comment 5 Haim 2012-02-05 08:29:05 UTC 
(In reply to comment #4)
> well it should only work for 3.2 cluster,
> if you don't have that in the UI, you may need to add that to the DB

changed cluster compatibility version from 3.0 to 3.2 and it works. 

please: change the error that Can_Do_Action returns to specify which action (not $ action), and what is the required compatibility  version (3.2 and above).
Comment 6 Michael Pasternak 2012-02-05 08:48:14 UTC 
Haim, why you opening bug on API if you know this is BE issue?
Comment 7 Haim 2012-02-05 09:07:30 UTC 
(In reply to comment #6)
> Haim, why you opening bug on API if you know this is BE issue?

we thought its an API fault, now we know differently.
Comment 8 Shahar Havivi 2012-02-13 15:18:40 UTC 
(In reply to comment #5)
> (In reply to comment #4)
> > well it should only work for 3.2 cluster,
> > if you don't have that in the UI, you may need to add that to the DB
> 
> changed cluster compatibility version from 3.0 to 3.2 and it works. 
> 
> please: change the error that Can_Do_Action returns to specify which action
> (not $ action), and what is the required compatibility  version (3.2 and
> above).

posted patch at:
http://gerrit.ovirt.org/#change,1868
Comment 9 Itamar Heim 2012-08-09 07:56:43 UTC 
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/
Note You need to log in before you can comment on or make changes to this bug.