[jbosstools-issues] [JBoss JIRA] (JBIDE-23291) If start of container fails on timeout, the status in server view is "Started, Synchronized"

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-23291:
-------------------------------------

We mark the server as started once vagrant says the cdk is started and the vagrant up command has completed.  If openshift is not running, we display a dialog to the user.  This is because if we mark the server as stopped, the 'stop' action on the server adapter won't be enabled. The user will then try to start it again, and vagrant will reply that it is already up. 

The question is, why is it timing out at all? 

> If start of container fails on timeout, the status in server view is "Started, Synchronized"
> --------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23291
>                 URL: https://issues.jboss.org/browse/JBIDE-23291
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.4.1.Final
>            Reporter: Aurélien Pupier
>            Assignee: Rob Stryker
>            Priority: Minor
>




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