[jbosstools-issues] [JBoss JIRA] (JBIDE-21170) Virtualbox could not be found by CDK adapter

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-21170:
---------------------------------------

Fred is right.

When I tested this yesterday, I still used all the workarounds I knew about, because the main thing we were trying to solve when debugging together on Monday was the non-working vagrant status (that is used to check if the server is running both before starting and once vagrant is up). So I entered the path to vagrant manually in launch config and I also set up the PATH variable Launch config's Environment tab. With this workaround I expected everything to work, but vagrant status still didn't work.

Then Rob fixed this by launching bash to get the full PATH and I confirmed that this fixed the issue with non-working vagrant status, but I still had the PATH variable set up in the launch config. (I would still be curious to know why vagrant status didn't work when vagrant location was correctly recognized.) I assumed that this new approach would provide the PATH for all parts of the tooling, so everything would work, but I failed to test this without my workarounds in place - I didn't realize that I should, I was focused on the vagrant status issue. My bad.

BTW, today when testing, I found another bug - when the credentials are missing, you're stuck on Starting - JBIDE-21335 .

So there are still these issues:
1. Path to vagrant is still empty on Mac and you need to set it manually. Could this also reuse the full path that you now get from bash? I understand that in order to fill the field you would need to get the location during runtime detection. But perhaps there is another way - maybe you could find vagrant on the first launch and then save it or something similar?
2. Even though you now get the full PATH and it fixed the vagrant status issue, it seems this PATH is not passed as an env var to the launch of vagrant up. (Currently you still need to define it manually.) Could that be fixed?

> Virtualbox could not be found by CDK adapter
> --------------------------------------------
>
>                 Key: JBIDE-21170
>                 URL: https://issues.jboss.org/browse/JBIDE-21170
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.3.1.Beta2
>
>
> After I set up a CDK server adapter and fixed the wrong path to vagrant in the launch config, I then started the server adapter and got this:
> Server CDK Server Adapter at localhost failed to start.
> Console:
> {code}
> The provider 'virtualbox' that was requested to back the machine
> 'default' is reporting that it isn't usable on this system. The
> reason is shown below:
> Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
> Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
> this to be available on the PATH. If VirtualBox is installed, please find the
> `VBoxManage` binary and add it to the PATH environmental variable.
> {code}
> Along with this, there was an Unhandled event loop exception in the error view:
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> 	at org.eclipse.swt.SWT.error(SWT.java:4491)
> 	at org.eclipse.swt.SWT.error(SWT.java:4406)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> 	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> 	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> 	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> 	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> 	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:520)
> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:359)
> 	at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:342)
> 	at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:327)
> 	at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
> 	at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
> 	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> 	... 23 more
> {code}
> In the command line, VBoxManage is accessible and it is located in /usr/local/bin/ and on my PATH.
> Max suggested I could try to start Eclipse from command line instead of double-clicking in Finder (which is the normal way to do it on Mac) and that helped.
> So for some reason when you start Eclipse using Eclipse.app from Finder, the PATH is incorrect.



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