[JBoss JIRA] (JBDS-3863) Platform Installer Hung after CDK install failed, no way to cancel, no info on error.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3863?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3863:
--------------------------------
Fix Version/s: 10.4.0.GA
(was: 10.4.0.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: 10.4.0.GA
>
> 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)
9 years
[JBoss JIRA] (JBDS-3756) Have two progress bars download and installation progress
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3756?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3756:
--------------------------------
Fix Version/s: 10.4.0.GA
(was: 10.4.0.AM2)
> Have two progress bars download and installation progress
> ---------------------------------------------------------
>
> Key: JBDS-3756
> URL: https://issues.jboss.org/browse/JBDS-3756
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Pete Muir
> Assignee: Denis Golovin
> Priority: Minor
> Labels: ui
> Fix For: 10.4.0.GA
>
>
> Most installers have a single progress bar that shows the overall progress, and then text which explains which component is being installed right now.
> Update:
> After discussion on backlog grooming session it seems reasonable to have two progress bars instead of one. Considering size of downloaded resources and time spend for downloading/installation we might have much longer installation time than now with single progress bar. Instead we can start downloading resources and install them as soon as download is finished. That would let us run installation in sequence and avoid problems with running two MSI installer at the same timed. Also that would save some time and do installation for smaller components while download for big ones is in progress.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4065) DevSuite 1.1 Installer unfriendly when 1.0 present
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4065:
--------------------------------
Fix Version/s: 10.4.0.GA
(was: 10.4.0.AM2)
> DevSuite 1.1 Installer unfriendly when 1.0 present
> --------------------------------------------------
>
> Key: JBDS-4065
> URL: https://issues.jboss.org/browse/JBDS-4065
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, platform-installer
> Affects Versions: 10.1.0.GA
> Environment: Windows 10, DevSuite Installer 1.0 had been run
> Reporter: Rick Wagner
> Assignee: Denis Golovin
> Fix For: 10.4.0.GA
>
>
> When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK.
> Observations:
> - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned).
> - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory.
> - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is?
> - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup.
> - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-3758) when something goes wrong, give user call to action / report of what went wrong
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3758?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3758:
--------------------------------
Fix Version/s: 10.4.0.GA
(was: 10.4.0.AM2)
> when something goes wrong, give user call to action / report of what went wrong
> -------------------------------------------------------------------------------
>
> Key: JBDS-3758
> URL: https://issues.jboss.org/browse/JBDS-3758
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.4.0.GA
>
> Attachments: jbds-install-ste-failed-progress-bar-keeps-moving.png
>
>
> I attempted to install from Setup-bundled-0.0.2-20160401-33.exe and while the installer was OK with my using my pre-installed JDK 8 in C:\Program Files\Java\jdk1.8.0_25 (or C:\Program Files\Java\jre1.8.0_25) it then ran into a problem using that JDK to install JBDS.
> I noticed the problem at about 12% on the progress bar but it was still moving along at 45% when I grabbed the screenshot (attached).
> If a failure occurs, perhaps *we could change the bar from blue to red and move it to 100%* ?
> Also, should there be a call to action for the user?
> Even something simple like "*go check in C:\DeveloperPlatform\install.log for what might have happened*" would be useful here.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4207) Request for administrator credentials should say DevSuite Installer not osascript
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4207?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4207:
--------------------------------
Fix Version/s: 10.4.0.GA
(was: 10.4.0.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: 10.4.0.GA
>
> 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)
9 years