[JBoss JIRA] (JBIDE-27019) Show in -> Web console option does not work at times
by André Dietisheim (Jira)
[ https://issues.redhat.com/browse/JBIDE-27019?page=com.atlassian.jira.plug... ]
André Dietisheim updated JBIDE-27019:
-------------------------------------
Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020, devex #181 Mar 2020, devex #182 Apr 2020, devex #183 May 2020 (was: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020, devex #181 Mar 2020, devex #182 Apr 2020, devex #183 May 2020, devex #184 May 2020)
> Show in -> Web console option does not work at times
> ----------------------------------------------------
>
> 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: Major
> Fix For: 4.16.x
>
>
> 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)
5 years, 10 months
[JBoss JIRA] (JBDS-4826) Installer do not extract EXE file
by Ondrej Dockal (Jira)
[ https://issues.redhat.com/browse/JBDS-4826?page=com.atlassian.jira.plugin... ]
Ondrej Dockal updated JBDS-4826:
--------------------------------
Story Points: 2
> Installer do not extract EXE file
> ----------------------------------
>
> Key: JBDS-4826
> URL: https://issues.redhat.com/browse/JBDS-4826
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.13.0.GA, 12.14.0.GA
> Reporter: Luca Preziati
> Assignee: Ondrej Dockal
> Priority: Major
> Fix For: 12.16.0.AM1
>
> Attachments: exe-missing.jpg, shared-libraries.jpg
>
>
> The installer do not extract exe.
> I extract manually from file I extract from this path the exe: codereadystudio-12.14.0.GA-installer-standalone.jar\devstudio\binary\com.jboss.devstudio.core.package.executable.win32.win32.x86_64_12.14.0.GA-v20200305-0719-B6018\
> !exe-missing.jpg|thumbnail!
> But the companion shared libraries are missing.
> !shared-libraries.jpg|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-27275) Update examples ITests to use EAP 7.3
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-27275:
-------------------------------------
Summary: Update examples ITests to use EAP 7.3
Key: JBIDE-27275
URL: https://issues.redhat.com/browse/JBIDE-27275
Project: Tools (JBoss Tools)
Issue Type: Task
Components: integration-tests, project-examples
Affects Versions: 4.16.0.AM1
Reporter: Josef Kopriva
Assignee: Zbyněk Červinka
Fix For: 4.16.0.AM1
EAP 7.3 is out, but we are still using old quickstarts.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata
by André Dietisheim (Jira)
[ https://issues.redhat.com/browse/JBIDE-21448?page=com.atlassian.jira.plug... ]
André Dietisheim commented on JBIDE-21448:
------------------------------------------
Downgrading to major severity (was: critical). This is even more true since we plan to fade out this tooling and replace it by odo tooling.
> Port Forwarding: Allow port-forwarding of ports not defined on pod metadata
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21448
> URL: https://issues.redhat.com/browse/JBIDE-21448
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jiri Pechanec
> Priority: Major
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.16.x
>
>
> Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too.
> And example is EAP CLI
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter
by André Dietisheim (Jira)
[ https://issues.redhat.com/browse/JBIDE-26599?page=com.atlassian.jira.plug... ]
André Dietisheim commented on JBIDE-26599:
------------------------------------------
[~jkopriva], [~jeffmaury] I think that we should either fix this or downgrade the severity. I tend to think that severity isn't critical?
> LiveReload does not work with OpenShift3 server adapter
> -------------------------------------------------------
>
> Key: JBIDE-26599
> URL: https://issues.redhat.com/browse/JBIDE-26599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, openshift
> Affects Versions: 4.11.0.Final
> Environment: oc cluster up 3.11 from Fedora repo
> Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre...
> Devstudio + installed livereload:
> Version: 12.11.0.GA
> Build id: GA-v20190321-1925-B4244
> Build date: 20190321-1925
> JDK 11.02 + F29
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Critical
> Fix For: 4.16.x
>
> Attachments: image-2019-03-27-10-30-34-801.png
>
>
> If I try to directly connect to livereload server there is an error message:
> {code:java}
> HTTP ERROR 500
> Problem accessing /. Reason:
> Server Error
> Caused by:
> java.lang.IllegalArgumentException: Invalid URI host: null (authority: null)
> at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506)
> at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438)
> at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> at org.eclipse.jetty.server.Server.handle(Server.java:502)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
> at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months