February 2020 - jbosstools-issues

[JBoss JIRA] (JBDS-4808) Add m2e-chromatic to the target platform

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBDS-4808?page=com.atlassian.jira.plugin... ] Stephane Bouchet updated JBDS-4808: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/342 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/333) > Add m2e-chromatic to the target platform > ---------------------------------------- > > Key: JBDS-4808 > URL: https://issues.redhat.com/browse/JBDS-4808 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: target-platform > Affects Versions: 12.13.0.GA > Reporter: Jeff MAURY > Assignee: Stephane Bouchet > Priority: Major > Fix For: 12.14.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27019) Show in -> Web console option does not work for CRC 1.3 as there is different end point url for this

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27019?page=com.atlassian.jira.plug... ] André Dietisheim edited comment on JBIDE-27019 at 2/10/20 6:02 AM: ------------------------------------------------------------------- [~odockal] that's odd, I cannot reproduce this. I get the console opened at the correct url, namely {code}https://console-openshift-console.apps-crc.testing/{code} The thing that makes me wondering is the following error message that you report: {code} com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap' at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149) at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) {code} The client library complains that it cannot retrieve config maps from the cluster. That's where the client library would fetch the url for the console from. Apparently this retrieval failed and Eclipse thus falled back to the default host url which is indeed {code}https://api.crc.testing:6443/{code} This retrieval should always succeed, config maps are a completely valid kind of resources, this shouldn't ever happen in an OpenShift cluster, that's very very unexpected. It would be "valid" that we cannot find the config map that stores the url for the console, but the client lib here fails in the prior step, it cannot even retrieve *ANY* config map. I thus suspect that your crc wasn't fully started. Can you still reproduce this bug? was (Author: adietish): [~odockal] that's odd, I cannot reproduce this. I get the console opened at the correct url, namely {code}https://console-openshift-console.apps-crc.testing/{code} The thing that makes me wondering is the following error message that you report: {code} com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap' at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149) at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) {code} The client library complains that it cannot retrieve config maps from the cluster. That's where the client library would fetch the url for the console from. Apparently this retrieval failed and Eclipse thus falled back to the default host url which is indeed {code}https://api.crc.testing:6443/{code}. This retrieval should always succeed, config maps are a completely valid kind of resources, this shouldn't ever happen in an OpenShift cluster, that's very very unexpected. It would be "valid" that we cannot find the config map that stores the url for the console, but the client lib here fails in the prior step, it cannot even retrieve *ANY* config map. I thus suspect that your crc wasn't fully started. Can you still reproduce this bug? > Show in -> Web console option does not work for CRC 1.3 as there is different end point url for this > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-27019 > URL: https://issues.redhat.com/browse/JBIDE-27019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: André Dietisheim > Priority: Critical > Fix For: 4.14.0.Final > > > Show in -> Web Console does not work for Openshift connection created from CRC 1.3 version as the Server's url (OS 4.2 endpoint - https://api.crc.testing:6443/) does not work for web console access. The correct one is https://console-openshift-console.apps-crc.testing/. > I got this error stack trace, btw: > {code} > eclipse.buildId=12.14.0.AM1-v20200123-0055-B5802 > java.version=11.0.5 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/odockal/workspace_12140AM1-0123/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.core.jobs > Error > Mon Jan 27 15:12:23 CET 2020 > An internal error occurred during: "Retrieving console for https://api.crc.testing:6443...". > com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap' > at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149) > at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:297) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:271) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:239) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:406) > at com.openshift.internal.restclient.capability.server.Console.getOpenShift4ConsoleUrl(Console.java:93) > at com.openshift.internal.restclient.capability.server.Console.getOpenShift4ConsoleUrl(Console.java:107) > at com.openshift.internal.restclient.capability.server.Console.getConsoleUrl(Console.java:64) > at org.jboss.tools.openshift.core.connection.Connection.getConsoleURL(Connection.java:381) > at org.jboss.tools.openshift.internal.ui.handler.OpenInWebConsoleHandler.lambda$0(OpenInWebConsoleHandler.java:61) > at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:164) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27019) Show in -> Web console option does not work for CRC 1.3 as there is different end point url for this

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27019?page=com.atlassian.jira.plug... ] André Dietisheim commented on JBIDE-27019: ------------------------------------------ [~odockal] that's odd, I cannot reproduce this. I get the console opened at the correct url, namely {code}https://console-openshift-console.apps-crc.testing/{code} The thing that makes me wondering is the following error message that you report: {code} com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap' at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149) at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) {code} The client library complains that it cannot retrieve config maps from the cluster. That's where the client library would fetch the url for the console from. Apparently this retrieval failed and Eclipse thus falled back to the default host url which is indeed {code}https://api.crc.testing:6443/{code}. This retrieval should always succeed, config maps are a completely valid kind of resources, this shouldn't ever happen in an OpenShift cluster, that's very very unexpected. It would be "valid" that we cannot find the config map that stores the url for the console, but the client lib here fails in the prior step, it cannot even retrieve *ANY* config map. I thus suspect that your crc wasn't fully started. Can you still reproduce this bug? > Show in -> Web console option does not work for CRC 1.3 as there is different end point url for this > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-27019 > URL: https://issues.redhat.com/browse/JBIDE-27019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: André Dietisheim > Priority: Critical > Fix For: 4.14.0.Final > > > Show in -> Web Console does not work for Openshift connection created from CRC 1.3 version as the Server's url (OS 4.2 endpoint - https://api.crc.testing:6443/) does not work for web console access. The correct one is https://console-openshift-console.apps-crc.testing/. > I got this error stack trace, btw: > {code} > eclipse.buildId=12.14.0.AM1-v20200123-0055-B5802 > java.version=11.0.5 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/odockal/workspace_12140AM1-0123/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.core.jobs > Error > Mon Jan 27 15:12:23 CET 2020 > An internal error occurred during: "Retrieving console for https://api.crc.testing:6443...". > com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap' > at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149) > at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:297) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:271) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:239) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:406) > at com.openshift.internal.restclient.capability.server.Console.getOpenShift4ConsoleUrl(Console.java:93) > at com.openshift.internal.restclient.capability.server.Console.getOpenShift4ConsoleUrl(Console.java:107) > at com.openshift.internal.restclient.capability.server.Console.getConsoleUrl(Console.java:64) > at org.jboss.tools.openshift.core.connection.Connection.getConsoleURL(Connection.java:381) > at org.jboss.tools.openshift.internal.ui.handler.OpenInWebConsoleHandler.lambda$0(OpenInWebConsoleHandler.java:61) > at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:164) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27045) Update odo in JBossTools to 1.1.0

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27045?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27045: ------------------------------------- Sprint: devex #179 Jan/Feb 2020 > Update odo in JBossTools to 1.1.0 > --------------------------------- > > Key: JBIDE-27045 > URL: https://issues.redhat.com/browse/JBIDE-27045 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.0.Final > > > JBossTools ask you to download odo, if you do not have installed odo or you have unsupported version. > Right now it asks to download 1.0.3, but last stable is 1.1.0. > https://github.com/openshift/odo/releases/tag/v1.1.0 > Tested in: > Red Hat CodeReady Studio > Version: 12.14.0.GA > Build id: GA-v20200210-0355-B5882 > Build date: 20200210-0355 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27044) Openshift ODO view: ODO login does not work

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27044?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-27044: ------------------------------------ Do you have Service Catalog in your cluster ? If not should be renamed as better handling service catalog > Openshift ODO view: ODO login does not work > ------------------------------------------- > > Key: JBIDE-27044 > URL: https://issues.redhat.com/browse/JBIDE-27044 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.14.0.Final > > Attachments: image-2020-02-10-10-00-58-714.png, image-2020-02-10-10-01-50-975.png, image-2020-02-10-10-03-05-163.png > > > Tested in: > Red Hat CodeReady Studio > Version: 12.14.0.GA > Build id: GA-v20200210-0355-B5882 > Build date: 20200210-0355 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27020) Cannot build jbosstools-openshift on our bare metal Mac OS CI machines

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27020?page=com.atlassian.jira.plug... ] Josef Kopriva reassigned JBIDE-27020: ------------------------------------- Assignee: Josef Kopriva (was: André Dietisheim) > Cannot build jbosstools-openshift on our bare metal Mac OS CI machines > ---------------------------------------------------------------------- > > Key: JBIDE-27020 > URL: https://issues.redhat.com/browse/JBIDE-27020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, qa > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.14.0.Final > > > Cannot build jbosstools-openshift on our Mac Os machines. > Ends up with: > {code} > 13:24:43 [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64} > 13:24:43 [ERROR] Cannot resolve project dependencies: > 13:24:43 [ERROR] You requested to install 'org.eclipse.equinox.p2.iu; com.basistech.m2e.code.quality.checkstyle.feature.feature.group 1.1.3' but it could not be found > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27020) Cannot build jbosstools-openshift on our bare metal Mac OS CI machines

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27020?page=com.atlassian.jira.plug... ] Josef Kopriva updated JBIDE-27020: ---------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.x) > Cannot build jbosstools-openshift on our bare metal Mac OS CI machines > ---------------------------------------------------------------------- > > Key: JBIDE-27020 > URL: https://issues.redhat.com/browse/JBIDE-27020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, qa > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.14.0.Final > > > Cannot build jbosstools-openshift on our Mac Os machines. > Ends up with: > {code} > 13:24:43 [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64} > 13:24:43 [ERROR] Cannot resolve project dependencies: > 13:24:43 [ERROR] You requested to install 'org.eclipse.equinox.p2.iu; com.basistech.m2e.code.quality.checkstyle.feature.feature.group 1.1.3' but it could not be found > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27045) Update odo in JBossTools

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-27045: ------------------------------------- Summary: Update odo in JBossTools Key: JBIDE-27045 URL: https://issues.redhat.com/browse/JBIDE-27045 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.14.0.Final Reporter: Josef Kopriva Assignee: Stephane Bouchet Fix For: 4.14.0.Final JBossTools ask you to download odo, if you do not have installed odo or you have unsupported version. Right now it asks to download 1.0.3, but last stable is 1.1.0. https://github.com/openshift/odo/releases/tag/v1.1.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27045) Update odo in JBossTools to 1.1.0

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27045?page=com.atlassian.jira.plug... ] Josef Kopriva updated JBIDE-27045: ---------------------------------- Summary: Update odo in JBossTools to 1.1.0 (was: Update odo in JBossTools) > Update odo in JBossTools to 1.1.0 > --------------------------------- > > Key: JBIDE-27045 > URL: https://issues.redhat.com/browse/JBIDE-27045 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.0.Final > > > JBossTools ask you to download odo, if you do not have installed odo or you have unsupported version. > Right now it asks to download 1.0.3, but last stable is 1.1.0. > https://github.com/openshift/odo/releases/tag/v1.1.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27045) Update odo in JBossTools to 1.1.0

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27045?page=com.atlassian.jira.plug... ] Josef Kopriva updated JBIDE-27045: ---------------------------------- Description: JBossTools ask you to download odo, if you do not have installed odo or you have unsupported version. Right now it asks to download 1.0.3, but last stable is 1.1.0. https://github.com/openshift/odo/releases/tag/v1.1.0 Tested in: Red Hat CodeReady Studio Version: 12.14.0.GA Build id: GA-v20200210-0355-B5882 Build date: 20200210-0355 was: JBossTools ask you to download odo, if you do not have installed odo or you have unsupported version. Right now it asks to download 1.0.3, but last stable is 1.1.0. https://github.com/openshift/odo/releases/tag/v1.1.0 > Update odo in JBossTools to 1.1.0 > --------------------------------- > > Key: JBIDE-27045 > URL: https://issues.redhat.com/browse/JBIDE-27045 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.0.Final > > > JBossTools ask you to download odo, if you do not have installed odo or you have unsupported version. > Right now it asks to download 1.0.3, but last stable is 1.1.0. > https://github.com/openshift/odo/releases/tag/v1.1.0 > Tested in: > Red Hat CodeReady Studio > Version: 12.14.0.GA > Build id: GA-v20200210-0355-B5882 > Build date: 20200210-0355 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 February 2020