[ 
https://issues.apache.org/jira/browse/LIBCLOUD-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Devin Bayer updated LIBCLOUD-708:
---------------------------------
    Description: 
Amazon can return a InstanceState of 'stopping' and when libcloud receives that 
it translates it to UNKNOWN, but we would like to at least report the state to 
the user.

class BaseEC2NodeDriver(NodeDriver):
    NODE_STATE_MAP = {
        'pending': NodeState.PENDING,
        'running': NodeState.RUNNING,
        'shutting-down': NodeState.UNKNOWN,
        'terminated': NodeState.TERMINATED
    }

See http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_InstanceState.html

  was:
Amazon can return a InstanceState of 'stopping' and when libcloud receives that 
it throws a KeyError since it's not in the NODE_STATE_MAP. It should at least 
treat these states as unknown.

class BaseEC2NodeDriver(NodeDriver):
    NODE_STATE_MAP = {
        'pending': NodeState.PENDING,
        'running': NodeState.RUNNING,
        'shutting-down': NodeState.UNKNOWN,
        'terminated': NodeState.TERMINATED
    }

See http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_InstanceState.html


> Support 'stopping' and 'stopped' InstanceState
> ----------------------------------------------
>
>                 Key: LIBCLOUD-708
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-708
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Core
>            Reporter: Devin Bayer
>
> Amazon can return a InstanceState of 'stopping' and when libcloud receives 
> that it translates it to UNKNOWN, but we would like to at least report the 
> state to the user.
> class BaseEC2NodeDriver(NodeDriver):
>     NODE_STATE_MAP = {
>         'pending': NodeState.PENDING,
>         'running': NodeState.RUNNING,
>         'shutting-down': NodeState.UNKNOWN,
>         'terminated': NodeState.TERMINATED
>     }
> See 
> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_InstanceState.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to