March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21844) Deploying specific docker images doesn't always result in a deployment on openshift

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21844?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21844: --------------------------------------- [~mlabuda][~maxandersen] please try again with the latest code. Fixed tracing issue by JBIDE-21867 which should now allow you to enable the trace logs and see the traffic from the rest client. > Deploying specific docker images doesn't always result in a deployment on openshift > ----------------------------------------------------------------------------------- > > Key: JBIDE-21844 > URL: https://issues.jboss.org/browse/JBIDE-21844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > > If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. > If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20602) docker image deploys have no way to get debug/log info

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20602?page=com.atlassian.jira.plugi... ] Jeff Cantrill closed JBIDE-20602. --------------------------------- Resolution: Rejected > docker image deploys have no way to get debug/log info > ------------------------------------------------------ > > Key: JBIDE-20602 > URL: https://issues.jboss.org/browse/JBIDE-20602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > > when deploy app via docker I don't seem to be able to get any logs or info about status. > web console says it is deployed/running with a yellow triangle but the weburl gives a 503 - service not available. > So what now ? how can users get logs/info about what went wrong ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20602) docker image deploys have no way to get debug/log info

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20602?page=com.atlassian.jira.plugi... ] Jeff Cantrill closed JBIDE-20602. --------------------------------- Resolution: Done > docker image deploys have no way to get debug/log info > ------------------------------------------------------ > > Key: JBIDE-20602 > URL: https://issues.jboss.org/browse/JBIDE-20602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > > when deploy app via docker I don't seem to be able to get any logs or info about status. > web console says it is deployed/running with a yellow triangle but the weburl gives a 503 - service not available. > So what now ? how can users get logs/info about what went wrong ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21559) Pod Log: should be able to select a container to show logs if pod contains more than 1 containers

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21559?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21559: --------------------------------------- merged into 4.3.x cherry-picked into master > Pod Log: should be able to select a container to show logs if pod contains more than 1 containers > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-21559 > URL: https://issues.jboss.org/browse/JBIDE-21559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBoss OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: openshift_v3, pod_log > Fix For: 4.4.0.Alpha1 > > > The existing issue: > 1.EXEC: Deploy a pod which contains more than 1 containers > 2.EXEC: Expand the related service tree view in "OpenShift Explorer" > 3.EXEC: Right click above pod -> click "Pod Log..." > 4.ASSERT: Will meet some errors in "Console" window like "Error from server: a container name must be specified for pod logging-kibana-1-icxl2" > So, we need find a method for user to specify a container to show logs when the pod has more than 1 containers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21616: ------------------------------------- [~snjeza] are you able to help with this issue? > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21866) Liberalize some astools API for re-use

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21866?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21866: ----------------------------------- Assignee: Rob Stryker Resolution: Done this was merged > Liberalize some astools API for re-use > -------------------------------------- > > Key: JBIDE-21866 > URL: https://issues.jboss.org/browse/JBIDE-21866 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > In order to allow openshift to use (but also override pieces of) our incremental deployment, we must liberalize a few methods from private to protected, and add a few superclasses for extending to avoid code duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21705) update tools.jboss.org/usage with error reporting tracking details

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21705?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21705: ------------------------------------ Max threw a PR up for this. Should we merge it or wait until AERI stuff is confirmed to work (JBDS-3566, JBDS-3600)? https://github.com/jbosstools/jbosstools-website/pull/553 > update tools.jboss.org/usage with error reporting tracking details > ------------------------------------------------------------------ > > Key: JBIDE-21705 > URL: https://issues.jboss.org/browse/JBIDE-21705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, usage > Reporter: Max Rydahl Andersen > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > usage page should not just talk about Google analytics, but aslo about error reporting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21877 at 3/16/16 1:35 PM: ------------------------------------------------------------------------ NPE in error log is an evidence of a bug, it should be fixed. To show a tree item, or a message is a solution that can be applied only after the bug is fixed for the code calling authentication could catch a specific exception that explains the problem. NPE is not good for analysing because it is not specific and just because it can be fixed upstream. In this case exception is thrown at request for authorization context. It is a role of the context to answer if user is authorized, or if his token expired. So, ideally, the context should be returned without any exceptions, at least when the problem is the expired token. was (Author: scabanovich): NPE in error log is an evidence of a bug, it should be fixed. To show a tree item, or a message is a solution that can be applied only after the bug is fixed for the code calling authentication could catch a specific exception that explains the problem. NPE is not good for analysing because it is not specific and just because it can be fixed upstream. > Make error message shown in OpenShift Explorer for outdated token more user friendly > ------------------------------------------------------------------------------------ > > Key: JBIDE-21877 > URL: https://issues.jboss.org/browse/JBIDE-21877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: connection, openshift_v3 > > When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log > {code} > There was an error retrieving children in the OpenShift explorer > java.lang.NullPointerException > at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124) > at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113) > at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69) > at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184) > at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43) > at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154) > at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557) > at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275) > at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) > at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) > at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) > at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99) > at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226) > at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376) > at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21874) OpenShift master branch is not compiling any more

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21874?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21874: ---------------------------------------- We need to fix compilation problems ASAP. Failing tests in master or/and some broken functionality (in master) can be fixed later. It's not so urgent while we are working on 4.3.1. > OpenShift master branch is not compiling any more > ------------------------------------------------- > > Key: JBIDE-21874 > URL: https://issues.jboss.org/browse/JBIDE-21874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: build, jenkins > Fix For: 4.4.0.Alpha1 > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1199/console} > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 11:47 min > [INFO] Finished at: 2016-03-15T22:47:06-04:00 > [INFO] Final Memory: 117M/733M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (default-compile) on project org.jboss.tools.openshift.express.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[44] > [ERROR] import org.eclipse.egit.core.AdaptableFileTreeIterator; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.eclipse.egit.core.AdaptableFileTreeIterator cannot be resolved > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1253] > [ERROR] AdaptableFileTreeIterator fileTreeIterator = new AdaptableFileTreeIterator( > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] AdaptableFileTreeIterator cannot be resolved to a type > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1253] > [ERROR] AdaptableFileTreeIterator fileTreeIterator = new AdaptableFileTreeIterator( > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] AdaptableFileTreeIterator cannot be resolved to a type > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1452] > [ERROR] return getComparator().compare(e1, e2); > [ERROR] ^^^^^^^ > [ERROR] The method compare(capture#5-of ? super String, capture#5-of ? super String) in the type Comparator<capture#5-of ? super String> is not applicable for the arguments (Object, Object) > [ERROR] 4 problems (4 errors) > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21874) OpenShift master branch is not compiling any more

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21874?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21874: ----------------------------------- Priority: Blocker (was: Critical) > OpenShift master branch is not compiling any more > ------------------------------------------------- > > Key: JBIDE-21874 > URL: https://issues.jboss.org/browse/JBIDE-21874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: build, jenkins > Fix For: 4.4.0.Alpha1 > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1199/console} > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 11:47 min > [INFO] Finished at: 2016-03-15T22:47:06-04:00 > [INFO] Final Memory: 117M/733M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (default-compile) on project org.jboss.tools.openshift.express.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[44] > [ERROR] import org.eclipse.egit.core.AdaptableFileTreeIterator; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.eclipse.egit.core.AdaptableFileTreeIterator cannot be resolved > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1253] > [ERROR] AdaptableFileTreeIterator fileTreeIterator = new AdaptableFileTreeIterator( > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] AdaptableFileTreeIterator cannot be resolved to a type > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1253] > [ERROR] AdaptableFileTreeIterator fileTreeIterator = new AdaptableFileTreeIterator( > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] AdaptableFileTreeIterator cannot be resolved to a type > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1452] > [ERROR] return getComparator().compare(e1, e2); > [ERROR] ^^^^^^^ > [ERROR] The method compare(capture#5-of ? super String, capture#5-of ? super String) in the type Comparator<capture#5-of ? super String> is not applicable for the arguments (Object, Object) > [ERROR] 4 problems (4 errors) > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016