[JBoss JIRA] (JBDS-3862) Platform installer failed to detect existing Cygwin install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3862?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3862:
-----------------------------------
Assignee: Denis Golovin
> Platform installer failed to detect existing Cygwin install
> -----------------------------------------------------------
>
> Key: JBDS-3862
> URL: https://issues.jboss.org/browse/JBDS-3862
> Project: Red Hat Developer Studio (DevStudio)
> 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
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.0.0.Alpha1
>
>
> 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
[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 commented on JBDS-3863:
-------------------------------------
This is most likely related to disk space shortage.
Installer should check for available disk space before continue with installation and translate error messages from cmd error out to UI.
> 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 Developer Studio (DevStudio)
> 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
[JBoss JIRA] (JBIDE-22005) Log console: Unexpected EOF in pod log
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22005:
--------------------------------
Story Points: 1
Sprint: devex #113 April 2016
> Log console: Unexpected EOF in pod log
> --------------------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22005) Log console: Unexpected EOF in pod log
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-22005.
---------------------------------
Resolution: Cannot Reproduce Bug
> Log console: Unexpected EOF in pod log
> --------------------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3862) Platform installer failed to detect existing Cygwin install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3862?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3862:
-------------------------------------
There is mo detection for cygwin yet.
cygwin is installed to get ssh, rsync and scp.
There are several options how to check:
1. If cygwin/bin is in PATH 'where ssh' should do the trick; also it supposed to check rsync and scp
2. Check windows registry if cygwin is in list of installed applications;
3. Ask for location where required utils are installed.
> Platform installer failed to detect existing Cygwin install
> -----------------------------------------------------------
>
> Key: JBDS-3862
> URL: https://issues.jboss.org/browse/JBDS-3862
> Project: Red Hat Developer Studio (DevStudio)
> 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
> Fix For: 10.0.0.Alpha1
>
>
> 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
[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-674:
----------------------------------
correct.
> Deprecate 'SOA 5.x Compatibility' tooling
> -----------------------------------------
>
> Key: JBTIS-674
> URL: https://issues.jboss.org/browse/JBTIS-674
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.0.Final, 9.0.0.GA
>
> Attachments: dep1.png, dep2.png, dep3.png, dep4.png, dep5.png
>
>
> The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
> org.guvnor.tools.feature
> org.jboss.tools.esb.feature
> org.jboss.tools.jbpm3.feature
> org.jboss.tools.jbpm.common.feature
> org.jboss.tools.jbpm.convert.feature
> The runtime detector features will not be deprecated:
> org.jboss.tools.runtime.drools.detector.feature
> org.jboss.tools.runtime.esb.detector.feature
> org.jboss.tools.runtime.jbpm.detector.feature
> FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20346:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> Jts quickstart (EAP 6.4) contains XML validation errors
> -------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.jboss.org/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Fix For: 4.4.x
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22005) Log console: Unexpected EOF in pod log
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22005:
---------------------------------------
I haven't spotted it since then, I would consider this one resolved as "out of date" or "cannot reproduce".
> Log console: Unexpected EOF in pod log
> --------------------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months