[
https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi...
]
Martin Malina updated JBIDE-22604:
----------------------------------
Workaround Description:
The way this was fixed for CDK 2.1 and devstudio 10 means that by default, sshfs (shared
folder) will not be used. There is a custom Vagrantfile with sshfs configured, but if you
use it with devstudio, you will still experience this issue - cdk will not start properly
in devstudio.
If you still want to use sshfs in devstudio, there is a workaround:
1. Start CDK with sshfs setup from CLI:
{code}
cd components/rhel/misc/shared_folder/rhel-ose
vagrant up
{code}
2. Set up CDK in devstudio and start it
Devstudio will notice it's already running and so it will mark it as Started
immediately, thus circumventing the whole startup which would fail in this case. You can
then use the cdk environment as normally - openshift connection and docker connection will
both work normally.
CDK server adapter stuck at starting
------------------------------------
Key: JBIDE-22604
URL:
https://issues.jboss.org/browse/JBIDE-22604
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, upstream
Affects Versions: 4.4.0.Final
Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe
devstudio 10.0.0.GA-a
CDK 2.1.RC3
Reporter: Jan Richter
Assignee: Rob Stryker
Priority: Blocker
Fix For: 4.4.0.Final
I have installed the development suite using the all-in-1 installer (on 3 different
windows machines now). Every time I try to start CDK using the server adapter it gets
stuck on 'starting'.
In fact the CDK does start up, openshift is running, but no connection is created + the
server adapter is marked as starting and the job (starting CDK) is spinning until it hits
the timeout.
Strange thing is - stopping the job/server adapter at this point will first create the
desired openshift connection and then CDK wil stop.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)