[
https://issues.apache.org/jira/browse/DTACLOUD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411369#comment-13411369
]
Christian Karnath commented on DTACLOUD-257:
--------------------------------------------
Hi Marios,
the ON-issues are strange. The issue regarding listing all instances happened
to me either until I created an instance via sunstone at
http://sunstone.c12g.com. After deleting the instance via sunstone this issue
was gone:
curl -H "X-Deltacloud-Driver: opennebula" -H "X-Deltacloud-Provider:
http://occi.c12g.com"; -v -u "USER:PASS"
http://localhost:3001/api/instances?format=xml
* About to connect() to localhost port 3001 (#0)
* Trying 127.0.0.1... connected
* Connected to localhost (127.0.0.1) port 3001 (#0)
* Server auth using Basic with user 'USER'
> GET /api/instances?format=xml HTTP/1.1
> Authorization: Basic PASS
> User-Agent: curl/7.21.6 (x86_64-pc-linux-gnu) libcurl/7.21.6 OpenSSL/1.0.0e
> zlib/1.2.3.4 libidn/1.22 librtmp/2.3
> Host: localhost:3001
> Accept: */*
> X-Deltacloud-Driver: opennebula
> X-Deltacloud-Provider: http://occi.c12g.com
>
< HTTP/1.1 200 OK
< ETag: "570ed38a6c6833d613702672e262c5ed"
< X-Frame-Options: sameorigin
< X-Backend-Runtime: 0.357523918151855
< X-XSS-Protection: 1; mode=block
< Content-Type: application/xml
< Date: Wed, 11 Jul 2012 09:46:55 GMT
< Content-Length: 65
< Server: Apache-Deltacloud/1.0.0
< Cache-Control: max-age=0, private, must-revalidate
< Connection: keep-alive
<
<?xml version='1.0' encoding='utf-8' ?>
<instances>
</instances>
* Connection #0 to host localhost left intact
* Closing connection #0
Moreover I couldn't reproduce the stop-issue. Stopping (and starting/rebooting)
an ON-instance just works fine at the moment.
Another issue I currently have with ON is that the destroy-action isn't
populated:
<instance href='http://localhost:3001/api/instances/2723' id='2723'>
<name>one-2723</name>
<owner_id>karnath</owner_id>
<image href='http://localhost:3001/api/images/0' id='0'></image>
<realm href='http://localhost:3001/api/realms/ONE' id='ONE'></realm>
<state>STOPPED</state>
<hardware_profile href='http://localhost:3001/api/hardware_profiles/small'
id='small'>
</hardware_profile>
<actions>
<link href='http://localhost:3001/api/instances/2723/start' method='post'
rel='start' />
</actions>
<public_addresses></public_addresses>
<private_addresses></private_addresses>
<storage_volumes></storage_volumes>
</instance>
> 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
>
> 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
