You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@deltacloud.apache.org by "Michal Fojtik (JIRA)" <ji...@apache.org> on 2010/11/23 12:33:14 UTC

[jira] Commented: (DTACLOUD-9) deltacloud answers with redirect (302) if you try to start a stopped instance on ec2

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

Michal Fojtik commented on DTACLOUD-9:
--------------------------------------

Hi Andre,

Fix for this issue is now available in our mailing list. Thanks for reporting that.

  -- Michal

> 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: David Lutterkort
>
> 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.
-
You can reply to this email to add a comment to the issue online.