[jbosstools-issues] [JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server

[Robert Terzi (JIRA)]

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

Robert Terzi commented on JBDS-3866:
------------------------------------

(This is probably way out of date, given I reported this bug 10+ months ago.)

To be clear, the bug was about incorrect "state information" between JBDS and vagrant that was caused by an rsync or other file sync step/provisioning error while waiting for the vagrant box to come up.   Testing this would require a vagrant box setup that will fail during the 'up' process.  

At this point, I'd say to close this bug,  But, it would be good to check if any of the test cases cover vagrant file sync. problems during 'up' and verify that state/error messages are accurate enough to let the user know what went wrong, and to stop the problematic box in order to try again.



> vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
> ----------------------------------------------------------------------------------------
>
>                 Key: JBDS-3866
>                 URL: https://issues.jboss.org/browse/JBDS-3866
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 9.1.0.Beta1
>         Environment: Windows 7/64 bit.
> (previous installs of CDK and dependencies)
>            Reporter: Robert Terzi
>            Assignee: Rob Stryker
>             Fix For: 10.4.0.AM2
>
>
> vagrant up through the CDK server tooling failed because of an rsync problem.  The tooling lost track of the state of the vagrant box.  The vagrant box couldn't be stopped from inside of Eclipse.
> The vagrant up failed because of an error with rsync.  Something was confused about the user's home directory.  It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist. 
> The CDK server was shown as 'Started, Sychronized'.   
> The error message appeared in the server console tab.  However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either.
> Synchronized seems misleading here, since no files had been sync'd yet.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)