Trying to start a stopped EC2 instance results in infinite starting task

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.