deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Karnath (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-257) opennebula driver stop instance request
Date Wed, 11 Jul 2012 13:16:34 GMT


Christian Karnath commented on DTACLOUD-257:

After applying the patch /instances works fine (as it did before in my environment), but with
this patch applied requesting /images returns a 500. 

curl -H "X-Deltacloud-Driver: opennebula" -H "X-Deltacloud-Provider:"
-v -u USER:PASS http://localhost:3001/api/images?format=xml

<?xml version='1.0' encoding='utf-8' ?>
<error status='500' url='/api/images?format=xml'>
  <backend driver='opennebula' provider=''>
  <message><![CDATA[REXML::Element is not a valid input stream.  It must walk
  like either a String, an IO, or a Source.]]></message>
    <![CDATA[/usr/lib/ruby/1.8/rexml/source.rb:21:in `create_from'
    /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:133:in `stream='

> opennebula driver stop instance request
> ---------------------------------------
>                 Key: DTACLOUD-257
>                 URL:
>             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
> I am running ruby 1.8.7 and requesting with cURL:
> curl -H "X-Deltacloud-Driver: opennebula" -H "X-Deltacloud-Provider:"
-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:!default.jspa
For more information on JIRA, see:


View raw message