[JBoss JIRA] (JBIDE-21610) [cdk] Current installer in windows bundles vagrant.bat, not vagrant.exe
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21610?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21610:
---------------------------------------
I checked now with a recent installation from the pdk installer - in launch config of cdk, I can see vagrant.exe is used. So I guess we no longer use vagrant.bat. But in any case, it works. Closing.
> [cdk] Current installer in windows bundles vagrant.bat, not vagrant.exe
> ------------------------------------------------------------------------
>
> Key: JBIDE-21610
> URL: https://issues.jboss.org/browse/JBIDE-21610
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> In order to locate vagrant on windows after using the pdk installer, we must expand the list of extensions searched for to include .bat.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21843) CDK Poller always fails on OSX
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21843?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21843.
---------------------------------
Works for me, closing. Let us know if you see this again.
> CDK Poller always fails on OSX
> ------------------------------
>
> Key: JBIDE-21843
> URL: https://issues.jboss.org/browse/JBIDE-21843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: OSX
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> Starting the CDK on OSX always fails. Whether it was already started from CLI or not.
> The vagrant up command is properly executed, you can see the output in the console, but it ends up with a message "Server CDK Server Adapter at localhost failed to start."
> I traced the problem back to:
> {noformat}
> VagrantPoller.parseOutput(String[]) line: 220
> VagrantPoller.onePing(IServer, String) line: 160
> VagrantPoller.onePing(IServer) line: 138
> VagrantPoller.getCurrentStateSynchronous(IServer) line: 114
> CDKLaunchController$2.run() line: 222
> {noformat}
> In parseOutput, the value of lines is :
> [1457536005,,error-exit,Vagrant::Errors::ProviderNotUsable,The provider 'virtualbox' that was requested to back the machine\n'cdk' is reporting that it isn't usable on this system. The\nreason is shown below:\n\nVagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.\nVagrant uses the `VBoxManage` binary that ships with VirtualBox%!(VAGRANT_COMMA) and requires\nthis to be available on the PATH. If VirtualBox is installed%!(VAGRANT_COMMA) please find the\n`VBoxManage` binary and add it to the PATH environmental variable.]
> this is not properly parsed as it later goes into this block
> {code}
> Collection<VagrantStatus> stats = status.values();
> if( stats.size() == 0 ) {
> return IStatus.ERROR;
> }
> {code}
> And the message in the lines is lost completely
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21810) Respect .cdk password
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21810?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21810:
---------------------------------------
For some reason this did not work for me yesterday when I tried this on Windows - [~jrichter1] installed the whole thing using the installer and then I started with a running JBDS with CDK configured. It had a name like rhel-ose, so I'm pretty sure that it was detected automatically.
When I started cdk (after changing the red hat account from jrichter to mmalina1, but this shouldn't have any effect on the OpenShift connection, right?), I *think* I was shown the certificate prompt right away but not sure. But what I'm sure of is that when I tried to expand the OpenShift connection in OpenShift Explorer, I was shown the dialog and had to enter credentials. I verified that the .cdk marker was there and contained both login and password for openshift.
We will try this again today when a new build of the installer is ready.
For now I checked this on OS X where I detected the cdk setup from openshift-vagrant repo which includes the .cdk marker file with everything and it worked fine - I didn't have to enter credentials for openshift.
> Respect .cdk password
> ---------------------
>
> Key: JBIDE-21810
> URL: https://issues.jboss.org/browse/JBIDE-21810
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> Respect the values in .cdk for password, and change default username/pass to openshift-dev/devel
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22113) CDK shutdown always goes to Forcing shutdown of VM on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22113?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22113:
---------------------------------------
I'm sorry, but it disappeared :( Yesterday I could see the force shutdown on windows in jbds several times. So I tried "vagrant halt" from command line and it was a graceful shutdown. Then I went home. I woke the windows laptop up from sleep and tried again - this time there is no forceful shutdown in jbds :(
> CDK shutdown always goes to Forcing shutdown of VM on Windows
> -------------------------------------------------------------
>
> Key: JBIDE-22113
> URL: https://issues.jboss.org/browse/JBIDE-22113
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> On OS X, when I stop CDK in JBDS, I get this in the console:
> ==> default: Unregistering box with vagrant-registration...
> ==> default: Attempting graceful shutdown of VM...
> And a few seconds later, the server adapter shows "Stopped".
> Today while testing on Windows I noticed that it behaves differently.
> It first displays these two lines, but it keeps "Stopping". And eventually there is another line in the console which says:
> ==> default: Forcing shutdown of VM...
> After this, the server adapter shows "Stopped".
> So for some unknown reason, on Windows the graceful shutdown fails to work.
> This is JBDS+CDK installed from the latest windows installer (built April 4th).
> It would be good to see if others see this on Windows as well or not.
> Interestingly, when I just tried "vagrant halt" from cygwin instead of in JBDS, it stops normally - graceful shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22113) CDK shutdown always goes to Forcing shutdown of VM on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22113?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22113:
---------------------------------------
I'm not aware of any impact this could have. I thought we were merely running vagrant halt in the tools, so I wonder what may cause this.
> CDK shutdown always goes to Forcing shutdown of VM on Windows
> -------------------------------------------------------------
>
> Key: JBIDE-22113
> URL: https://issues.jboss.org/browse/JBIDE-22113
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> On OS X, when I stop CDK in JBDS, I get this in the console:
> ==> default: Unregistering box with vagrant-registration...
> ==> default: Attempting graceful shutdown of VM...
> And a few seconds later, the server adapter shows "Stopped".
> Today while testing on Windows I noticed that it behaves differently.
> It first displays these two lines, but it keeps "Stopping". And eventually there is another line in the console which says:
> ==> default: Forcing shutdown of VM...
> After this, the server adapter shows "Stopped".
> So for some unknown reason, on Windows the graceful shutdown fails to work.
> This is JBDS+CDK installed from the latest windows installer (built April 4th).
> It would be good to see if others see this on Windows as well or not.
> Interestingly, when I just tried "vagrant halt" from cygwin instead of in JBDS, it stops normally - graceful shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years