deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Karnath (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-456) Opennebula: Error occurs when requesting all instances against opennebula
Date Fri, 01 Mar 2013 09:37:12 GMT


Christian Karnath commented on DTACLOUD-456:

Hi Ronelle,

Thank you for doing a first test drive. It seems that the opennebula dummy cloud at
is not running anymore. I get the following error message when authenticating against sunstone
( "OpenNebula is not running or there was a server exception. Please
check the server logs."

While writing and testing the patch I could authenticate against that cloud and even could
access the API further than the top level collections. In the meantime stuff seems to be broken/offline
there. The homepage claims that account requests are no longer available (
and that the preferred way for a "try out" is to run an opennebula sandbox on your own (

I just setup a cloud sandbox with kvm for testing purposes. If you like I and can hand out
you some creds for an additional test drive. Just ping me on IRC.


> Opennebula: Error occurs when requesting all instances against opennebula
> -------------------------------------------------------------------------
>                 Key: DTACLOUD-456
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>            Reporter: Christian Karnath
>            Assignee: Ronelle Landy
>         Attachments: 0001-Opennebula-Fix-when-computehash-INSTANCE_TYPE-is-nil.patch
> The following error occurs when requesting all instances against opennebula and one instance
has no ‘INSTANCE_TYPE’ set:
> E, [2013-02-06T17:42:50.830852 #12715] ERROR -- 500: [Deltacloud::Exceptions::BackendError]
Internal Server Error
> - - [06/Feb/2013 17:42:50] "GET /api/instances HTTP/1.1" opennebula
500 93 0.5609
> The attached patch will fix this issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message