April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22077) Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22077?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22077: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag > ---------------------------------------------------------------------------- > > Key: JBIDE-22077 > URL: https://issues.jboss.org/browse/JBIDE-22077 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > On a machine where ~/.kube is missing or no insecure-skip-tls-verify was set from CLI, pod logs and port forwarding are failing with "Unable to connect to the server: x509: certificate signed by unknown authority" > There are 2 problems: > - the restclient is not passing the options through the oc binary > - the portforwarding code in eclipse is not sending the options to the client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22077) Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22077?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-22077. ----------------------------------- Resolution: Done > Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag > ---------------------------------------------------------------------------- > > Key: JBIDE-22077 > URL: https://issues.jboss.org/browse/JBIDE-22077 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > On a machine where ~/.kube is missing or no insecure-skip-tls-verify was set from CLI, pod logs and port forwarding are failing with "Unable to connect to the server: x509: certificate signed by unknown authority" > There are 2 problems: > - the restclient is not passing the options through the oc binary > - the portforwarding code in eclipse is not sending the options to the client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-629) Check/Modify RuntimeDetection tests

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-629: ---------------------------------- Summary: Check/Modify RuntimeDetection tests Key: JBTIS-629 URL: https://issues.jboss.org/browse/JBTIS-629 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Affects Versions: 4.3.0.Beta1 Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Fix For: 4.3.0.Final [~apodhrad] Andrej raised concerns about they stability/operability -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22073) Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22073?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22073. --------------------------------- Verified in JBDS 9.1.0.GA build ID B477. > Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag > ---------------------------------------------------------------------------- > > Key: JBIDE-22073 > URL: https://issues.jboss.org/browse/JBIDE-22073 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.CR1 > > > On a machine where ~/.kube is missing or no insecure-skip-tls-verify was set from CLI, pod logs and port forwarding are failing with "Unable to connect to the server: x509: certificate signed by unknown authority" > There are 2 problems: > - the restclient is not passing the options through the oc binary > - the portforwarding code in eclipse is not sending the options to the client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22077) Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22077: ------------------------------------- Summary: Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag Key: JBIDE-22077 URL: https://issues.jboss.org/browse/JBIDE-22077 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon Assignee: Fred Bricon Priority: Blocker Fix For: 4.3.1.CR1 On a machine where ~/.kube is missing or no insecure-skip-tls-verify was set from CLI, pod logs and port forwarding are failing with "Unable to connect to the server: x509: certificate signed by unknown authority" There are 2 problems: - the restclient is not passing the options through the oc binary - the portforwarding code in eclipse is not sending the options to the client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21981) Error during rsync

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21981: --------------------------------------- On JBDS 9.1.0.CR1 respin-a build I am able to reproduce with steps in "Steps to Reproduce" similar behaviour. Server adapter is not in Debugging state, but there is an warning with nested error in error log. Also changes are successfully published via rsync (content of web page has changed to reflect changes in local workspace). Warning: {code}Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/mlabuda/workspaces/910GA/.metadata/.plugins/org.jboss.ide.eclipse.as.core/eap-app_at_OpenShift_3_(10.1.2.2)/deploy org.eclipse.core.runtime.CoreException: Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/mlabuda/workspaces/910GA/.metadata/.plugins/org.jboss.ide.eclipse.as.core/eap-app_at_OpenShift_3_(10.1.2.2)/deploy at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:71) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Contains: OpenShiftBinaryCapability process exited: could not make way for new regular file: ROOT.war rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1637) [generator=3.1.1] error: exit status 23 {code} Nested error {code}Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/mlabuda/workspaces/910GA/.metadata/.plugins/org.jboss.ide.eclipse.as.core/eap-app_at_OpenShift_3_(10.1.2.2)/deploy An exception stack trace is not available.{code} It is not so critical as original issue, but still its an issue. Do you wanna reopen this one and lower priority or to create a new one? > Error during rsync > ------------------ > > Key: JBIDE-21981 > URL: https://issues.jboss.org/browse/JBIDE-21981 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.CR1 > > > While testing the debugging support on the server adapter, I got the following error: > {code} > Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy > OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66) > rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9] > error: exit status 23 > {code} > The content of the {{.../deploy}} directory was: > {code} > drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./ > drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../ > -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt > drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/ > -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed > -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying > -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar > -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed > -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3753) Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3753?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3753: ----------------------------------- [~nickboldt], apparently I am not the novelist you are - that title deserves a nobel prize. > Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway > --------------------------------------------------------------------------------------- > > Key: JBDS-3753 > URL: https://issues.jboss.org/browse/JBDS-3753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Setup-bundled-0.0.2-20160401-28 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > Using bundled installer build 28 - confirmation page will not let me use the bundled JDK if it detects a pre-existing JDK somewhere else. > Once the installation is triggered, JDK goes straight to finished (not a problem under these circumstances) but JBDS fails right away and the log says: > {noformat} > Fri, 01 Apr 2016 07:20:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zSE006.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds failed to install: Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT > {noformat} > So basically, I can't get it to install the bundled JDK but it will still try to use it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22076) Application pod is not visible after build is completed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22076?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22076. --------------------------------- Fix Version/s: 4.3.1.CR1 Resolution: Cannot Reproduce Bug Ah. I tried to reproduce it in JDBS and then I found out that update of nightly OpenShift build in JBT did not work - after checking for updates and updating and restarting JBT, there was still some old version of JBT. This is not happening in JBDS 9.1.0.CR1 respin-a. > Application pod is not visible after build is completed > ------------------------------------------------------- > > Key: JBIDE-22076 > URL: https://issues.jboss.org/browse/JBIDE-22076 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > > When I create a new application on OpenShift from template, e.g. eap template, there is a running build pod. Once this build pod finish successfully, there is spinned up an application pod but it is not visible in OpenShift Explorer automatically. Refresh of a project is necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22076) Application pod is not visible after build is completed

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22076: ------------------------------------- Summary: Application pod is not visible after build is completed Key: JBIDE-22076 URL: https://issues.jboss.org/browse/JBIDE-22076 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda When I create a new application on OpenShift from template, e.g. eap template, there is a running build pod. Once this build pod finish successfully, there is spinned up an application pod but it is not visible in OpenShift Explorer automatically. Refresh of project is necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22076) Application pod is not visible after build is completed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22076?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22076: ---------------------------------- Labels: openshift_v3 (was: ) > Application pod is not visible after build is completed > ------------------------------------------------------- > > Key: JBIDE-22076 > URL: https://issues.jboss.org/browse/JBIDE-22076 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > When I create a new application on OpenShift from template, e.g. eap template, there is a running build pod. Once this build pod finish successfully, there is spinned up an application pod but it is not visible in OpenShift Explorer automatically. Refresh of project is necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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