[jbosstools-issues] [JBoss JIRA] (JBIDE-23179) "poweroff" not recognized as a vagrant state in master

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-23179:
---------------------------------------

[~rob.stryker], can you explain the implications of this to me please?
Does this mean that before, if vagrant status returned "not created", the tooling would not properly categorise this as stopped?
So for example if you start cdk in eclipse, then "vagrant destroy" in cli and then stop in eclipse, it would not work before, but works now? (Indeed, it does work for me.)
And one more question, you parse the vagrant status output here: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.cdk.server/src/org/jboss/tools/openshift/cdk/server/core/internal/adapter/VagrantPoller.java#L265
I don't fully understand exactly how you parse it. But I wonder, the constant is "not_created" whereas the vagrant status will return "not created" (with space). Is that taken into account?

> "poweroff" not recognized as a vagrant state in master
> ------------------------------------------------------
>
>                 Key: JBIDE-23179
>                 URL: https://issues.jboss.org/browse/JBIDE-23179
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.4.2.AM1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.4.2.AM1
>
>
> A vagrant machine in state not_created is not recognized  at all. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)