November 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-3834) Install fail - what next?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3834: -------------------------------- Fix Version/s: 11.2.0.AM2 (was: 11.x) > Install fail - what next? > ------------------------- > > Key: JBDS-3834 > URL: https://issues.jboss.org/browse/JBDS-3834 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Misha Ali > Assignee: Denis Golovin > Fix For: 11.2.0.AM2 > > Attachments: error.PNG, fail_install.PNG > > > Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4369) Provide a .exe for uninstaller on Windows

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4369?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4369. ----------------------------- > Provide a .exe for uninstaller on Windows > ----------------------------------------- > > Key: JBDS-4369 > URL: https://issues.jboss.org/browse/JBDS-4369 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 11.2.0.AM1 > > > currently it is a .ps1 file, this is very uncommon -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4584) Categorize components to install

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4584?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4584. ----------------------------- > Categorize components to install > -------------------------------- > > Key: JBDS-4584 > URL: https://issues.jboss.org/browse/JBDS-4584 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM1 > > > the list is starting to be bigger, it might useful to categorize them, not sure around which criteria. > This came to my mind while thinking that it would be easier if I have a single checkbox for installing Fuse for all possible platforms -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3806) Installer - reduce footer height to reveal more content

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3806?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3806. ----------------------------- > Installer - reduce footer height to reveal more content > ------------------------------------------------------- > > Key: JBDS-3806 > URL: https://issues.jboss.org/browse/JBDS-3806 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM1 > > Attachments: confirm.png > > > The footer on the confirm page would look better if it cut into the display of one of the components to be installed. Also, remove the transparency. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3863) Platform Installer Hung after CDK install failed, no way to cancel, no info on error.

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3863?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3863. ----------------------------- > 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.2.0.AM1 > > 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.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3642 at 11/22/17 1:58 AM: --------------------------------------------------------------- Latest version install components one by one and offer 'Show log' button to debug installation errors. Resolving. was (Author: dgolovin): Latest version install components one by one and offer 'Show log' buttod to debug installation errors. Resolving. > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM2 > > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3642. --------------------------------- Resolution: Done Latest version install components one by one and offer 'Show log' buttod to debug installation errors. Resolving. > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM2 > > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3642: -------------------------------- Fix Version/s: 11.2.0.AM2 (was: 11.x) > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM2 > > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4335) Clearly mark third party components available for installation on confirmation page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4335?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-4335. --------------------------------- Resolution: Won't Fix > Clearly mark third party components available for installation on confirmation page > ----------------------------------------------------------------------------------- > > Key: JBDS-4335 > URL: https://issues.jboss.org/browse/JBDS-4335 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.AM1, 10.4.0.GA > Reporter: Denis Golovin > Assignee: Mohit Suman > Labels: ui > Fix For: 11.2.0.AM2 > > > Current UI does not distinguish Red Hat products and third party components available for installation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4335) Clearly mark third party components available for installation on confirmation page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4335?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4335: -------------------------------- Fix Version/s: 11.2.0.AM2 (was: 11.x) > Clearly mark third party components available for installation on confirmation page > ----------------------------------------------------------------------------------- > > Key: JBDS-4335 > URL: https://issues.jboss.org/browse/JBDS-4335 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.AM1, 10.4.0.GA > Reporter: Denis Golovin > Assignee: Mohit Suman > Labels: ui > Fix For: 11.2.0.AM2 > > > Current UI does not distinguish Red Hat products and third party components available for installation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2017