February 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-25759) CDK Server adapter editor: layout glitches for "--skip-(un)registration"-checkbox

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25759: ---------------------------------------- Summary: CDK Server adapter editor: layout glitches for "--skip-(un)registration"-checkbox Key: JBIDE-25759 URL: https://issues.jboss.org/browse/JBIDE-25759 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cdk, openshift Affects Versions: 4.5.2.AM2 Reporter: Andre Dietisheim Attachments: screenshot-1.png The layout for the checkboxes to skip the registration/unregistration are not well horizontally aligned with the "Registration:" label. They are pushed to the bottom by 1 line: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25611: ------------------------------------- Comment: was deleted (was: [~jeffmaury] in terms of naming, these are the exact same templates nodejs-mongo-persistent templates on cdk and openshift online respectively. They could differ in terms of content though. If that's true then the Online version would still be broken.) > Server adapter: timeouts when starting into "Debug" on OpenShift Online > ----------------------------------------------------------------------- > > Key: JBIDE-25611 > URL: https://issues.jboss.org/browse/JBIDE-25611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.3.AM2 > > Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, image-2018-01-26-00-49-39-691.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png > > > # ASSERT: have an account on OpenShift Online > # EXEC: create a new application via template nodejs-mongo-persistent > # EXEC: have the project imported into the workspace and the server adapter for it created > # ASSERT: you have a new server adapter for your app in state [stopped] > # EXEC: start the adapter into "Debug" > Result: > The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog: > !error-waiting-for-new-pod.png! > In the Eclipse log you'll find the following: > {code} > org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25611: ------------------------------------- Comment: was deleted (was: This is quite odd. When launching into an existing pod that is set to debugging the tooling will error complaining about a missing debug port: !port-missing.png! Eclipse is missing the debugging port in port forwarding and thus fails to start it.. !image-2018-01-24-18-58-29-159.png! The port is *NOT* exposed by the REST service (making the Eclipse port forwarding incapable to forward to the port it doesn't see): !pod-ports-online.png! When looking into the pod I see it launching node with the debug flag and port {code} PID TTY STAT TIME COMMAND 1 ? Ssl 0:00 node /opt/rh/rh-nodejs6/root/usr/bin/nodemon --debug=5858 {code} If I launch the port forwarding manually via "oc" and launch the nodejs debugger in Eclipse I see the debugging fine. In comparison in the CDK the pod is exposing the debugging port: !pod-ports-cdk.png! [~jeffmaury] ideas?) > Server adapter: timeouts when starting into "Debug" on OpenShift Online > ----------------------------------------------------------------------- > > Key: JBIDE-25611 > URL: https://issues.jboss.org/browse/JBIDE-25611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.3.AM2 > > Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, image-2018-01-26-00-49-39-691.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png > > > # ASSERT: have an account on OpenShift Online > # EXEC: create a new application via template nodejs-mongo-persistent > # EXEC: have the project imported into the workspace and the server adapter for it created > # ASSERT: you have a new server adapter for your app in state [stopped] > # EXEC: start the adapter into "Debug" > Result: > The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog: > !error-waiting-for-new-pod.png! > In the Eclipse log you'll find the following: > {code} > org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20569: ------------------------------------- Fix Version/s: 4.5.3.AM3 (was: 4.5.3.AM2) > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, ux > Fix For: 4.5.3.AM3 > > Attachments: import-application.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25303 at 2/28/18 10:53 AM: -------------------------------------------------------------------- I can and then cannot reproduce the permissions issue that I faced in https://issues.jboss.org/browse/JBIDE-25303?focusedCommentId=13519836&pag... in CDK 3.3 (it happens inconsistently). I cannot determine yet what the reason might be. The anyuid addons is always enabled for me and doesnt seem involved. When the permission issue occurrs the error looks very similar to what we see in OpenShift Online JBIDE-25700 was (Author: adietish): I can and then cannot reproduce the permissions issue that I faced in https://issues.jboss.org/browse/JBIDE-25303?focusedCommentId=13519836&pag... in CDK 3.3. I cannot determine yet what the reason might be. The anyuid addons is always enabled for me and doesnt seem involved. When the permission issue occurrs the error looks very similar to what we see in OpenShift Online JBIDE-25700 > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.3.AM3 > > Attachments: Image+Pasted+at+2018-1-16+10-58.png, fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > ** -Dfabric8.generator.from=fabric8/s2i-java > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25700) Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25700: ------------------------------------------ in JBIDE-25303 I get the same permission problems (non-consistently though) running the same example in a local CDK > Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online > --------------------------------------------------------------------------- > > Key: JBIDE-25700 > URL: https://issues.jboss.org/browse/JBIDE-25700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Priority: Critical > Labels: online, springboot > Fix For: 4.5.3.AM3 > > > neither with open.paas.redhat.com > so only when using the CDK. > it seems to be due to the fact that the user in the pod are not the same. > Jeff said: > {quote} > For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF > The user permissions on those folders are the following: > /deployments: writable by user jboss and group root > /deployments/BOOT-INF: writable by user jboss readable only by group root > /deployments/META-INF: writable by user jboss readable only by group root > The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25733) Tests failures in OpenShift for Java9

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25733?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25733: ------------------------------------------ merged into master, jenkins build is green. > Tests failures in OpenShift for Java9 > ------------------------------------- > > Key: JBIDE-25733 > URL: https://issues.jboss.org/browse/JBIDE-25733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: Java9 > Fix For: 4.5.3.AM2 > > > Some unit tests are failing because of the Powermock dependency -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25751) Client: release and use 5.9.5.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25751?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-25751. ------------------------------------ Resolution: Done re-closing > Client: release and use 5.9.5.Final > ----------------------------------- > > Key: JBIDE-25751 > URL: https://issues.jboss.org/browse/JBIDE-25751 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift-restclient-java > Fix For: 4.5.3.AM2 > > > In JBIDE-25734 we introduced a new client version 5.9.4-SNAPSHOT. So that clients in our tools releases can be indetifiable we should release and use 5.9.5.Final for AM2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25751) Client: release and use 5.9.5.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25751?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25751: ------------------------------------- Sprint: devex #145 February 2018 > Client: release and use 5.9.5.Final > ----------------------------------- > > Key: JBIDE-25751 > URL: https://issues.jboss.org/browse/JBIDE-25751 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift-restclient-java > Fix For: 4.5.3.AM2 > > > In JBIDE-25734 we introduced a new client version 5.9.4-SNAPSHOT. So that clients in our tools releases can be indetifiable we should release and use 5.9.5.Final for AM2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25700) Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25700: ------------------------------------- Fix Version/s: 4.5.3.AM3 (was: 4.5.3.AM2) > Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online > --------------------------------------------------------------------------- > > Key: JBIDE-25700 > URL: https://issues.jboss.org/browse/JBIDE-25700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Priority: Critical > Labels: online, springboot > Fix For: 4.5.3.AM3 > > > neither with open.paas.redhat.com > so only when using the CDK. > it seems to be due to the fact that the user in the pod are not the same. > Jeff said: > {quote} > For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF > The user permissions on those folders are the following: > /deployments: writable by user jboss and group root > /deployments/BOOT-INF: writable by user jboss readable only by group root > /deployments/META-INF: writable by user jboss readable only by group root > The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 February 2018