deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-317) Openstack driver understands only numeric part of instances ID
Date Thu, 06 Sep 2012 13:35:08 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449646#comment-13449646
] 

Marios Andreou commented on DTACLOUD-317:
-----------------------------------------

Hi Andrejs, I can't reproduce this against Essex.

Can you show me the output of 'all instances' and then for a specific instance. Are you seeing
something interesting/different in the nova logs now? (shouldn't be the same issue as before
since the 1.0.4 gem addressed that). What happens when you use the HTML UI for deltacloud
instead of curl?

thanks, marios
                
> Openstack driver understands only numeric part of instances ID  
> ----------------------------------------------------------------
>
>                 Key: DTACLOUD-317
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-317
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Native/Frontend
>         Environment: openstack Essex
> Ubuntu 12.04 server amd64  deltacloud-core 1.0.2
> installed using "gem install deltacloud-core"
>            Reporter: Andrejs Abele
>            Assignee: Marios Andreou
>
> I started deltacloud using this command
> "deltacloudd -i openstack  -r 10.196.2.84"
> Listing all instances works 
> "curl --user "username+tenant:pass" -H 'X-Deltacloud-Provider:http://nimbus01.sindice.net:5000/v2.0'
http://10.196.2.84:3001/api/instances?format=xml"
> but when  I try to get information about a certain instance 
> root@Development1:/home/administrator# curl --user "username+tenant:pass" -H 'X-Deltacloud-Provider:http://nimbus01.sindice.net:5000/v2.0'
http://10.196.2.84:3001/api/instances/104289a8-a5d0-46a7-8114-c4d7c3ee688d?format=xml
> <h1>Not Found</h1>
> on Essex side in logs can see, that only first numeric part of instances ID arrived
> Instances ID is  "104289a8-a5d0-46a7-8114-c4d7c3ee688d" but on Essex arrived only "104289"
> /var/log/nova/nova-api.log
>  
> 2012-09-06 11:14:55 INFO nova.api.openstack.wsgi [req-06da1ca6-8fc4-44e0-a6d7-14eaebf03ab3
13098b0fd6584ed488e41da792df7fc4 fc8b65df1f0748d198e6d99ae7ee9505] GET http://10.196.106.211:8774/v2/fc8b65df1f0748d198e6d99ae7ee9505/servers/104289
> 2012-09-06 11:14:55 DEBUG nova.api.openstack.wsgi [req-06da1ca6-8fc4-44e0-a6d7-14eaebf03ab3
13098b0fd6584ed488e41da792df7fc4 fc8b65df1f0748d198e6d99ae7ee9505] Empty body provided in
request from (pid=1518) get_body /usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py:705
> 2012-09-06 11:14:55 INFO nova.api.openstack.wsgi [req-06da1ca6-8fc4-44e0-a6d7-14eaebf03ab3
13098b0fd6584ed488e41da792df7fc4 fc8b65df1f0748d198e6d99ae7ee9505] HTTP exception thrown:
The resource could not be found.
> 2012-09-06 11:14:55 INFO nova.api.openstack.wsgi [req-06da1ca6-8fc4-44e0-a6d7-14eaebf03ab3
13098b0fd6584ed488e41da792df7fc4 fc8b65df1f0748d198e6d99ae7ee9505] http://10.196.106.211:8774/v2/fc8b65df1f0748d198e6d99ae7ee9505/servers/104289
returned with HTTP 404

--
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: http://www.atlassian.com/software/jira

Mime
View raw message