[
https://issues.apache.org/jira/browse/DTACLOUD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411449#comment-13411449
]
Marios Andreou commented on DTACLOUD-257:
-----------------------------------------
Hi Christian, I just cc'd you on an e-mail (on dev@deltacloud list also) to the
ON guys about the 'destroy only whilst running' issue - I think that *might* be
intended behaviour. The ON guys also gave us a patch which is attached here -
it solved the 'list all instances' problem for me. I'd be grateful if you could
try it out and ACK/NACK accordingly (either here or on the dev@deltacloud list).
thanks, marios
what do you think we should do with this ticket? if the attached patch is
approved should we resolve+close?
> opennebula driver stop instance request
> ---------------------------------------
>
> Key: DTACLOUD-257
> URL: https://issues.apache.org/jira/browse/DTACLOUD-257
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: ruby1.8, deltacloud-core-1.0.0, deltacloud-core-head
> Reporter: Christian Karnath
> Assignee: Marios Andreou
> Attachments:
> 0001-Updates-for-Opennebula-driver-brings-compatibility-f.patch
>
>
> When POSTing /api/instances/<inst>/stop on a running instance against the
> opennebula-driver the following error occurs:
> Deltacloud::ExceptionHandler::ProviderError - [VirtualMachineAction] Wrong
> state to perform action
> I am running ruby 1.8.7 and requesting with cURL:
> curl -H "X-Deltacloud-Driver: opennebula" -H "X-Deltacloud-Provider:
> http://occi.c12g.com"; -v -u xxx:yyy
> http://localhost:3001/api/instances/2660/stop -d" "
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
