[dev] [jira] [Commented] (LIBCLOUD-280) EC2 node state 'shutting-down' is mapped to TERMINATED state

["Tomaz Muraus (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LIBCLOUD-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545597#comment-13545597 ] 

Tomaz Muraus commented on LIBCLOUD-280:
---------------------------------------

I agree with your assessment and think that mapping 'shutting down' to UNKNOWN state is reasonable and more correct compared to what we currently do.

I will push this change to trunk later today.
                
> EC2 node state 'shutting-down' is mapped to TERMINATED state
> ------------------------------------------------------------
>
>                 Key: LIBCLOUD-280
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-280
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>            Reporter: Marcin Kuzminski
>              Labels: backward-incompatible
>
> Ec2 node map translates shutting-down state to TERMINATED, IMHO it's a bug. When you want to terminated instances, and then for example delete security group for those node you have to do it after nodes are actually terminated. Current code makes the instances that are being terminated indicated as already terminated. I think the mapping should be 'shutting-down': NodeState.UNKNOWN, as sen in other drivers for example in brightbox

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira