| Summary: | [ovirt] [engine-api] cancel-migrate: action is not supported | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Haim <hateya> |
| Component: | ovirt-engine-core | Assignee: | Shahar Havivi <shavivi> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | acathrow, iheim, mgoldboi, mpastern, shavivi, yeylon, ykaul |
| Target Milestone: | --- | ||
| Target Release: | 3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-09 07:56:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
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... Haim, what cluster version did you use? (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 ? 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 (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). Haim, why you opening bug on API if you know this is BE issue? (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. (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 closing ON_QA bugs as oVirt 3.1 was released: http://www.ovirt.org/get-ovirt/ |
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