deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramesh A (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (DTACLOUD-9) deltacloud answers with redirect (302) if you try to start a stopped instance on ec2
Date Wed, 07 Mar 2012 16:44:57 GMT

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

Ramesh A edited comment on DTACLOUD-9 at 3/7/12 4:44 PM:
---------------------------------------------------------

Verified and now Deltacloud API throws "501-Not Supported" error in the web ui (refer screenshot
"501-Not Supported.png") and Error message as "Deltacloud::ExceptionHandler::NotSupported
- start_instance capability not supported by backend Deltacloud::Drivers::EC2::EC2Driver"
in the UI and console.  This behaviour is observed for both terminated and stopped instance.
(Note: As of now we are not supporting the start feature for EC2 via deltacloud for EBS backed
instances) 
Verified from Web-UI and cURL.

Environment Details:
================
Deltacloud API 0.5.0 
commit a1a15d18882b385b2d1e2970fd18e67ff81dfebf
OS - Fedora -15, 16, RHEL - 6.2

Curl Output(XML):
============
[rananda@rananda deltacloud]$ curl -X POST --user "username:password" http://localhost:3003/api/instances/i-1b77d17f/start?format=xml
<error status='501' url='/api/instances/i-1b77d17f/start?format=xml'>
  <kind>backend_error</kind>
  <backend driver='ec2' provider='default'>
    <code>501</code>
  </backend>
  <message><![CDATA[start_instance capability not supported by backend Deltacloud::Drivers::EC2::EC2Driver]]></message>
  <request>
    <param name='format'>xml</param>
    <param name='captures'>Deltacloud::ExceptionHandler::NotSupported</param>
    <param name='splat'></param>
  </request>
</error>
[rananda@rananda deltacloud]$

Curl opuput (JSON):
==============
[rananda@rananda deltacloud]$ curl -X POST -H 'Accept: application/xml' --user "username:password"
http://localhost:3003/api/instances/i-1b77d17f/start?format=json
{"status":501,"message":"start_instance capability not supported by backend Deltacloud::Drivers::EC2::EC2Driver","url":"/api/instances/i-1b77d17f/start?format=json"}[rananda@rananda
deltacloud]$

Hence closing this issue
                
      was (Author: rananda):
    Verified and now Deltacloud API throws "501-Not Supported" error in the web ui (refer
screenshot "501-Not Supported.png") and Error message as "Deltacloud::ExceptionHandler::NotSupported
- start_instance capability not supported by backend Deltacloud::Drivers::EC2::EC2Driver"
in the UI and console.  This behaviour is observed for both terminated and stopped instance.
(Note: As of now we are not supporting the start feature for EC2 via deltacloud for EBS backed
instances) 
Verified from Web-UI and cURL.

Curl Output(XML):
============
[rananda@rananda deltacloud]$ curl -X POST --user "username:password" http://localhost:3003/api/instances/i-1b77d17f/start?format=xml
<error status='501' url='/api/instances/i-1b77d17f/start?format=xml'>
  <kind>backend_error</kind>
  <backend driver='ec2' provider='default'>
    <code>501</code>
  </backend>
  <message><![CDATA[start_instance capability not supported by backend Deltacloud::Drivers::EC2::EC2Driver]]></message>
  <request>
    <param name='format'>xml</param>
    <param name='captures'>Deltacloud::ExceptionHandler::NotSupported</param>
    <param name='splat'></param>
  </request>
</error>
[rananda@rananda deltacloud]$

Curl opuput (JSON):
==============
[rananda@rananda deltacloud]$ curl -X POST -H 'Accept: application/xml' --user "username:password"
http://localhost:3003/api/instances/i-1b77d17f/start?format=json
{"status":501,"message":"start_instance capability not supported by backend Deltacloud::Drivers::EC2::EC2Driver","url":"/api/instances/i-1b77d17f/start?format=json"}[rananda@rananda
deltacloud]$

Hence closing this issue
                  
> deltacloud answers with redirect (302) if you try to start a stopped instance on ec2
> ------------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-9
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-9
>             Project: DeltaCloud
>          Issue Type: Bug
>         Environment: deltacloud 0.0.9, REST API
>            Reporter: André Dietisheim
>            Assignee: Ramesh A
>         Attachments: 501-Not Supported.png
>
>
> if you try to start an instance on ec2 (REST API), deltacloud answers with a redirect
(302). IMHO the answer should be a 404, 405 or any other client error (4xx) since ec2 does
not allow to start instances that are stopped.
> concrete example:
> instance i-00e28a6d is stopped, but still visible on ec2. I now try to start it with
the Deltacloud REST API:
> Request to Deltacloud:
> POST /api/instances/i-00e28a6d/start HTTP/1.1
> Response from Deltacloud:
> Statuscode = 302
> Body = empty

--
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

       

Mime
View raw message