deltacloud-dev mailing list archives

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

     [ https://issues.apache.org/jira/browse/DTACLOUD-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ramesh A updated DTACLOUD-9:
----------------------------

    Attachment: 501-Not Supported.png
    
> 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