April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3862) Platform installer failed to detect existing Cygwin install

by Robert Terzi (JIRA)

[ https://issues.jboss.org/browse/JBDS-3862?page=com.atlassian.jira.plugin.... ] Robert Terzi commented on JBDS-3862: ------------------------------------ There is no way to tell the platform installer not to install a component. There was no way to tell it not to install Cygwin. > Platform installer failed to detect existing Cygwin install > ----------------------------------------------------------- > > Key: JBDS-3862 > URL: https://issues.jboss.org/browse/JBDS-3862 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit, > Cygwin 2.5.1 already installed in the detault location C:\cygwin. > Reporter: Robert Terzi > Priority: Minor > > The installer did not detect the existing Cygwin install in C:\Cygwin. > What test is used to determine if Cygwin is already installed? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server

by Robert Terzi (JIRA)

Robert Terzi created JBDS-3866: ---------------------------------- Summary: vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server Key: JBDS-3866 URL: https://issues.jboss.org/browse/JBDS-3866 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: cdk Affects Versions: 9.1.0.Beta1 Environment: Windows 7/64 bit. (previous installs of CDK and dependencies) Reporter: Robert Terzi vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse. The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist. The CDK server was shown as 'Started, Sychronized'. The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either. Synchronized seems misleading here, since no files had been sync'd yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22118) Application wizard: Should support "builder" images

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22118?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22118: ----------------------------------------------- [~jcantrill], you can improve abbreviating of items in the list by just setting to OpenShiftExplorerLabelProvider labelProvider a larger limit since wizard width definitely allows for that. Set labelProvider.setLabelLimit(100). To be exact, this label provider is hidden inside ObservableTreeItemLabelProvider, so you can either add the same method to it, or expose the inner provider. > Application wizard: Should support "builder" images > --------------------------------------------------- > > Key: JBIDE-22118 > URL: https://issues.jboss.org/browse/JBIDE-22118 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > Attachments: buildconfig page.png, page_1.png > > > I installed the following image stream: https://raw.githubusercontent.com/jboss-openshift/application-templates/m... > It contains several "builder" images. I would like to use jboss-eap70-openshift:1.3-Beta to build a JavaEE 7 application available at https://github.com/redhat-helloworld-msa/hello . But the Openshift plugin only shows "templates". > Openshift plugin should support "builder" images. These images contain "builder" on their tags. > Ref: Jan-5-2016 discussion: http://etherpad.corp.redhat.com/OpenShiftAndJBossStudio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3865) Platform installer should warn about known bad versions of Vagrant.

by Robert Terzi (JIRA)

Robert Terzi created JBDS-3865: ---------------------------------- Summary: Platform installer should warn about known bad versions of Vagrant. Key: JBDS-3865 URL: https://issues.jboss.org/browse/JBDS-3865 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: platform-installer Affects Versions: 9.1.0.Beta1 Environment: Windows 7/64 bit. Vagrant 1.8.1 installed Reporter: Robert Terzi Priority: Minor The platform installer should flag versions of Vagrant (and possibly other software) that are known to be bad. There should possibly be a black list. Vagrant 1.8.0 and 1.8.1 have a bunch of bugs, so they aren't recommended for CDK. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3864) Why is the platform installer installing pscp when Cygwin openssh scp is also installed?

by Robert Terzi (JIRA)

Robert Terzi created JBDS-3864: ---------------------------------- Summary: Why is the platform installer installing pscp when Cygwin openssh scp is also installed? Key: JBDS-3864 URL: https://issues.jboss.org/browse/JBDS-3864 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: platform-installer Affects Versions: 9.1.0.Beta1 Environment: Windows 7/64 bit. Reporter: Robert Terzi Priority: Optional Why does the platform installer install putty's pscp.ese when it also installs Cygwin's openssh which includes scp? A while back vagrant-service-manager had a dependency on pscp.exe for copying certificates, but I believe that was eliminated a while back. (around the time of the rename from adbinfo to service-manager). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 Robert Terzi (JIRA)

Robert Terzi created JBDS-3863: ---------------------------------- Summary: 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: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: platform-installer Affects Versions: 9.1.0.Beta1 Environment: Windows 7/64 bit. (Some components of previous manual CDK install on the system). Reporter: Robert Terzi Attachments: 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. This might have been due to disk space, but it's not clear/obvious from the log. 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 (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22255. --------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) Assignee: Rob Stryker Resolution: Done > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Minor > Labels: openshift_v3, server, ux > Fix For: 4.4.0.Alpha1 > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3862) Platform installer failed to detect existing Cygwin install

by Robert Terzi (JIRA)

Robert Terzi created JBDS-3862: ---------------------------------- Summary: Platform installer failed to detect existing Cygwin install Key: JBDS-3862 URL: https://issues.jboss.org/browse/JBDS-3862 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: platform-installer Affects Versions: 9.1.0.Beta1 Environment: Windows 7/64 bit, Cygwin 2.5.1 already installed in the detault location C:\cygwin. Reporter: Robert Terzi Priority: Minor The installer did not detect the existing Cygwin install in C:\Cygwin. What test is used to determine if Cygwin is already installed? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22259) Server Adapter: Debugging of OS 3 application creates a new replication controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22259: ------------------------------------------ I dont think that this is critical. It's annoying since you'd have to manually remove your replication controllers at some point, but that's far from being Critical imho. Setting it to major > Server Adapter: Debugging of OS 3 application creates a new replication controller > ---------------------------------------------------------------------------------- > > Key: JBIDE-22259 > URL: https://issues.jboss.org/browse/JBIDE-22259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22259) Server Adapter: Debugging of OS 3 application creates a new replication controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22259: ------------------------------------- Priority: Major (was: Critical) > Server Adapter: Debugging of OS 3 application creates a new replication controller > ---------------------------------------------------------------------------------- > > Key: JBIDE-22259 > URL: https://issues.jboss.org/browse/JBIDE-22259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016