]
Andre Dietisheim updated JBIDE-7365:
------------------------------------
Fix Version/s: LATER
(was: 3.2.0.CR1)
postponed fix since we need fixes in the deltacloud server. As soon as the server is
fixed, no changes are necessary in the client. The client offers those actions to the user
that he received in the server response (ex. you stop an instance, the server then
responds that start & destroy are available. In case of EC2 he should respond that no
actions are available).
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: LATER
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: