You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "André Dietisheim (JIRA)" <ji...@apache.org> on 2010/11/22 11:53:13 UTC
[jira] Created: (DTACLOUD-9) deltacloud answers with redirect (302)
if you try to start a stopped instance on ec2
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
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DTACLOUD-9) deltacloud answers with redirect (302)
if you try to start a stopped instance on ec2
Posted by "André Dietisheim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
André Dietisheim updated DTACLOUD-9:
------------------------------------
Description:
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
was: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
> 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
> 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.
[jira] Commented: (DTACLOUD-9) deltacloud answers with redirect
(302) if you try to start a stopped instance on ec2
Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] [Resolved] (DTACLOUD-9) deltacloud answers with redirect
(302) if you try to start a stopped instance on ec2
Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik resolved DTACLOUD-9.
----------------------------------
Resolution: Fixed
Assignee: Michal Fojtik (was: David Lutterkort)
This issue should be resolved now. Andre?
> 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: Michal Fojtik
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DTACLOUD-9) deltacloud answers with redirect
(302) if you try to start a stopped instance on ec2
Posted by "André Dietisheim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934814#action_12934814 ]
André Dietisheim commented on DTACLOUD-9:
-----------------------------------------
awesome, thanks!
> 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.
[jira] Issue Comment Edited: (DTACLOUD-9) deltacloud answers with
redirect (302) if you try to start a stopped instance on ec2
Posted by "André Dietisheim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934814#action_12934814 ]
André Dietisheim edited comment on DTACLOUD-9 at 11/23/10 6:50 AM:
-------------------------------------------------------------------
awesome, thanks!
IMHO DTACLOUD-8 and DTACLOUD-9 are not the same, but might have identical reasons in the implementation.
DTACLOUD-8 is about an action, that is reported to be available while it shouldn't.
DTACLOUD-9 is just a 'bug' in a general behavior. I'd expect a client error (4xx) if I request to perform a resource-transition that is not available.
Agree?
was (Author: adietisheim):
awesome, thanks!
> 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.
[jira] Updated: (DTACLOUD-9) deltacloud answers with redirect (302)
if you try to start a stopped instance on ec2
Posted by "André Dietisheim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
André Dietisheim updated DTACLOUD-9:
------------------------------------
Environment: deltacloud 0.0.9, REST API (was: deltacloud 0.0.9)
> 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.