[
https://issues.jboss.org/browse/JBIDE-23291?page=com.atlassian.jira.plugi...
]
Aurélien Pupier edited comment on JBIDE-23291 at 1/13/17 9:58 AM:
------------------------------------------------------------------
I don't think that we can say that it is "as expected", it is "as
designed" but we have a functional issue here. The status is "started,
synchronized" although the CDK server is not available.
What is "expected" is that the status is "synchronizing" and/or when
the timeout ends, some kind of "error" on connection.
Just looking for the vagrant status seems not enough.
was (Author: aurelien.pupier):
I don't think that we can say that it is "as expected", it is "as
designed" but we have a functional issue here. The status is "started,
synchronized" although the CDK server is not available.
What is "expected" is that the status is "synchronizing" and/or when
the timeout ends, some kind of "error" on connection.
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
Fix For: 4.4.2.Final
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)