[JBoss JIRA] (JBDS-4401) devsuite 1.4 installer hangs searching for installed components
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4401?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4401:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> devsuite 1.4 installer hangs searching for installed components
> ---------------------------------------------------------------
>
> Key: JBDS-4401
> URL: https://issues.jboss.org/browse/JBDS-4401
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Environment: DevSuite 1.4 installer on Windows 7 and Windows 10.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> On both windows 7 and windows 10, I'm running into cases where the devsuite 1.4 installer hangs in the looking for components stage. I can't click back, I can only click Cancel. When I cancel, I get a UAC message about the installer possibly not being installed correctly. However, I did get UAC prompt to run as admin when I first started the installer.
> Both machines have had previous installer 1.3 installs both successful and unsuccessful.
> If there is a log I'm not sure where to find it, since the destination directory hasn't been created yet.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-3863) Platform Installer Hung after CDK install failed, no way to cancel, no info on error.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3863?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3863:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Platform Installer Hung after CDK install failed, no way to cancel, no info on error.
> --------------------------------------------------------------------------------------
>
> Key: JBDS-3863
> URL: https://issues.jboss.org/browse/JBDS-3863
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 1.1.0.GA, 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> (Some components of previous manual CDK install on the system).
> Also Windows 10/64.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
> Attachments: box-add-fail-1.1.0-ga.txt, install.log, jbds-install-log-win7-error.txt
>
>
> Using the platform installer, CDK installation failed, progress shown as 99%. At this point the installer was hung.
> Note:
> * CDK install progress said Failed, with progress stuck at 99%.
> * There is no way to cancel out of the install.
> * There was no pop-up about error messages.
> * No indication of where to look for error messages/logs etc.was provided.
> * CDK was previously installed manually. However, the installer window didn't say a previous CDK installation was detected, but the log does show it deleted the previous cdkv2 box.
> From the log it looks like the box add command failed. When originally reported it might have been due to disk space, but it's not clear/obvious from the log. As of DevSuite 1.1.0 GA, the problems still exists if the vagrant box add command fails. Note: I've verified this isn't related to disk space and is a Vagrant problem.
> Note: after killing the installer and trying the `vagrant box add` command copied from the log file manually in Cygwin bash the box add command succeeded. The test system had 5-15 GB of free space between the installation started.
> Full log attached, excerpt here.
> Tue, 26 Apr 2016 18:05:38 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box
> Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box SUCCESS
> Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe
> Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe SUCCESS
> Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1
> Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS
> Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk
> Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk SUCCESS
> Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1
> Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS
> Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - postVagrantSetup called
> Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute command vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem"
> Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute options {
> "env": {
> "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;"
> }
> }
> Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Installing the 'c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem' plugin. This can take a few minutes...
> Installed the plugin 'vagrant-registration (1.2.1)'!
> Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" SUCCESS
> Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute command vagrant box remove cdkv2 -f
> Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute options {
> "env": {
> "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;"
> }
> }
> Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Removing box 'cdkv2' (v0) with provider 'virtualbox'...
> Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute vagrant box remove cdkv2 -f SUCCESS
> Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box"
> Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute options {
> "env": {
> "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;"
> }
> }
> Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box"
> The box failed to unpackage properly. Please verify that the box
> file you're trying to add is not corrupted and try again. The
> output from attempting to unpackage (if any):
> x box.ovf
> x Vagrantfile
> x vagrant-virtualbox-box.vmdk: Write failed
> x metadata.json
> bsdtar.EXE: Error exit delayed from previous errors.
> Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - The box failed to unpackage properly. Please verify that the box
> file you're trying to add is not corrupted and try again. The
> output from attempting to unpackage (if any):
> x box.ovf
> x Vagrantfile
> x vagrant-virtualbox-box.vmdk: Write failed
> x metadata.json
> bsdtar.EXE: Error exit delayed from previous errors.
> Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box"
> The box failed to unpackage properly. Please verify that the box
> file you're trying to add is not corrupted and try again. The
> output from attempting to unpackage (if any):
> x box.ovf
> x Vagrantfile
> x vagrant-virtualbox-box.vmdk: Write failed
> x metadata.json
> bsdtar.EXE: Error exit delayed from previous errors.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-4252) Installer waits for failed Virtualbox installation (MacOS)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4252?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4252:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Installer waits for failed Virtualbox installation (MacOS)
> ----------------------------------------------------------
>
> Key: JBDS-4252
> URL: https://issues.jboss.org/browse/JBDS-4252
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.2.0.GA
> Reporter: Andre Dietisheim
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM2
>
> Attachments: waiting-for-virtualbox-install-that-failed.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have VirtualBox 5.1.x running but the app is removed from the Applications folder
> # EXEC: launch installer, log in and select VirtualBox etc.
> Result:
> Installer fails to install VirtualBox.
> !waiting-for-virtualbox-install-that-failed.png!
> In the logs you see the following:
> {code}
> 0:233: execution error: installer: Error - The installer has detected running virtual machines. Please shut down all running VirtualBox machines and then restart the installation. (1)
> {code}
> The installer simply states "Failed". It would be nice if the installer could provide more details on why/what failed. Sparing me from having to inspect the logs.
> It simply states "Failed" for VirtualBox, the "Red Hat Container Development Kit" process is waiting for VirtualBox to get installed even though that failed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-3797) Installer: temporary files are not removed when window is closed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3797?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3797:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Installer: temporary files are not removed when window is closed
> ----------------------------------------------------------------
>
> Key: JBDS-3797
> URL: https://issues.jboss.org/browse/JBDS-3797
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer, upstream
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 11.0.0.AM2
>
>
> # download installer exe
> # run DeveloperPlatformInstaller*.exe
> # when installer's window opens, close the window
> # look into _C:\Users\yourusername\AppData\Local\Temp_
> result:
> Temp folder contains several files and directories with name starting *7zS*, with total size of about *1.7GB*, when you open start the installer multiple times, it appears multiple times in Temp
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-4207) Request for administrator credentials should say DevSuite Installer not osascript
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4207?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4207:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Request for administrator credentials should say DevSuite Installer not osascript
> ---------------------------------------------------------------------------------
>
> Key: JBDS-4207
> URL: https://issues.jboss.org/browse/JBDS-4207
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: known_issue
> Fix For: 11.0.0.AM2
>
> Attachments: osascript.png
>
>
> Current implementation use osascript (AppleScript Engine) to run installation for vagrant and virtualbox as administrator. The consequence is osascript name in standard login/password dialog.
> !osascript.png!
> It should say Red Hat Development Suite Installer" instead
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-4103) Prefer JDK over JRE as VM set in devstudio.ini
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4103?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4103:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Prefer JDK over JRE as VM set in devstudio.ini
> ----------------------------------------------
>
> Key: JBDS-4103
> URL: https://issues.jboss.org/browse/JBDS-4103
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM2
>
>
> When using JBDS, a lot of people will use Maven and having a JDK by default is better.
> It allows to launch Maven install with java compilation directly, without extra configuration.
> (as a side note, do we really want to set a vm? when the Vm is updated, the link is broken and we need to update it)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months