[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-7365) Trying to start a stopped EC2 instance results in infinite starting task

[Andre Dietisheim (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563110#comment-12563110 ] 

Andre Dietisheim edited comment on JBIDE-7365 at 11/18/10 4:31 PM:
-------------------------------------------------------------------

The behavior with the current client and current deltacloud (0.1.0) is that starting an ec2 instance results in an error (no infinite starting task any more).

Deltacloud destroys instances when they are stopped. This is intentional, it looks like ec2 cannot restore instances (unless they're EBS-backend instances which deltacloud can not handle). 
Unfortunately the answers deltacloud responds are not consitent either:

- if you stop an instance on EC2, you get START reported as available action. If you look at the aws console, you'll see that start is not available.
- If you try to start that instance, you get a 302 (redirect). You should get at 404! 

Any tries to get that working right (no start available for ec2 instances) looks like a dirty workaround to me. We need to have deltacloud 'fixed' or instructions from them.

      was (Author: adietish):
    The behavior with the current client and current deltacloud (0.1.0) is that starting an ec2 instance results in an error (no infinite starting task any more).

Deltacloud destroys instances when they are stopped. This is intentional, it looks like ec2 cannot restore instances (unless they're EBS-backend instances which deltacloud can not handle). 
Unfortunately the answers deltacloud responds are not consitent either:

- if you stop an instance on EC2, you get START reported as available action. If you look at the aws console, you'll see that start is not available.
- If you try to start that instance, you get a 302 (redirect). You should get at 404! 

Any tries to get that working right for the moment looks like a dirty workaround to me. We need to have deltacloud 'fixed' or instructions from them.
  
> Trying to start a stopped EC2 instance results in infinite starting task
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-7365
>                 URL: https://jira.jboss.org/browse/JBIDE-7365
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: deltacloud
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Jeff Johnston
>            Assignee: Andre Dietisheim
>             Fix For: 3.2.0.CR1
>
>
> Using deltacloud 0.0.7, when an EC2 instance is stopped, it is no longer listed as TERMINATED as it was
> in deltacloud 0.0.5.  Instead, it is listed as STOPPED and the REST interface reports that a START action is
> possible.  This is not true.  An EC2 instance, once stopped, is terminated and cannot be restarted.  The Deltacloud
> tools get the available actions from the REST interface and so if a user attempts to start the instance, the tools will
> allow this and set up a task to wait for the state to change from STOPPED, but this will never happen and the task remains in the
> task list indefinitely due to the fact that the task cannot be cancelled.
> The Deltacloud tools currently does not support cancelling state-change-wait tasks because they are necessary to keep
> the cached data up-to-date (e.g. we need to know when an instance in PENDING becomes RUNNING and if the user
> has stopped an instance, we need to know when it is officially STOPPED or TERMINATED as this affects available actions,
> for example.  The task continuously waits and refreshes the instance, waiting for a state change.  If a user requests another action,
> the current wait-task will be cancelled and the new one will take it's place (e.g. one can STOP a PENDING instance that hasn't
> achieved RUNNING state yet).
> A bug has been opened against Deltacloud server: https://bugzilla.redhat.com/show_bug.cgi?id=64285 regarding the invalid
> action/state settings for the stopped EC2 instance.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira