[
https://issues.jboss.org/browse/JBIDE-23010?page=com.atlassian.jira.plugi...
]
Brian Exelbierd commented on JBIDE-23010:
-----------------------------------------
So doing some very basic research, this appears to be a manifestation of the same issues
that were present in vagrant-sshfs.
In both of these plugins cases, I am not sure that blocking on these streams closing is a
good idea. The return code of vagrant, I believe, will tell you if the box started. If
these plugins later run into trouble and need to make an error report, DevStudio should be
able to react to that. As it is now, our fix consists of basically shunting error logging
off to the side and never telling DevStudio about problems if they arise.
We can probably get this fixed in landrush without too much trouble, however, we may
eventually need a plugin that is not so keen on this patch.
Is this something we can resolve on the DevStudio side?
landrush plugin prevents CDK server adapter from starting
---------------------------------------------------------
Key: JBIDE-23010
URL:
https://issues.jboss.org/browse/JBIDE-23010
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, upstream
Affects Versions: 4.4.1.AM3
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Today I downloaded cdk 2.2.rc1 [1], installed all the vagrant plugins from scratch. And
then I first started this from CLI - it wanted password for sudo to set up landrush.
(That's another concern I have: How will this work in devstudio? Probably it
won't.)
Then I stopped it, set up in devstudio and start there. Everything looks fine, but the
server adapter is stuck at "Starting...".
This is the console output:
{code}
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: [landrush] virtualbox requires an additional private network; adding it
==> default: [landrush] starting dns server
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Registering box with vagrant-registration...
==> default: Checking for guest additions in VM...
default: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
default:
default: This is not an error message; everything may continue to work properly,
default: in which case you may ignore this message.
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
[landrush] Using eth1 (172.28.128.3)
==> default: [landrush] adding machine entry: cdk.vm => 172.28.128.3
==> default: [landrush] adding static DNS entry: cdk => cdk.vm
[landrush] Using eth1 (172.28.128.3)
[landrush] Host DNS resolver config looks good.
==> default: Copying TLS certificates to
/Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
==> default: Mounting SSHFS shared folder...
==> default: Mounting folder via SSHFS: /Users/rasp => /Users/rasp
==> default: Checking Mount..
==> default: Checking Mount..
==> default: Folder Successfully Mounted!
==> default: Machine already provisioned. Run `vagrant provision` or use the
`--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still
run.
==> default: Running provisioner: shell...
default: Running: inline script
==> default: Running provisioner: shell...
default: Running: inline script
==> default:
==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of
memory.
==> default: To modify the number of cores and/or available memory set the environment
variables
==> default: VM_CPU respectively VM_MEMORY.
==> default:
==> default: You can now access the OpenShift console on:
https://openshift.cdk:8443/console
==> default:
==> default: To use OpenShift CLI, run:
==> default: $ vagrant ssh
==> default: $ oc login
==> default:
==> default: Configured users are (<username>/<password>):
==> default: openshift-dev/devel
==> default: admin/admin
==> default:
==> default: If you have the oc client library on your host, you can also login from
your host.
{code}
These are my plugins:
{code}
$ vagrant plugin list
landrush (1.1.1)
- Version Constraint: 1.1.1
vagrant-registration (1.2.3)
- Version Constraint: 1.2.3
vagrant-service-manager (1.3.0)
- Version Constraint: 1.3.0
vagrant-share (1.1.5, system)
vagrant-sshfs (1.2.0)
- Version Constraint: 1.2.0
{code}
[1]
http://cdk-builds.usersys.redhat.com/builds/weekly/12-Aug-2016.rc1/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)