February 2018 - jbosstools-issues

[JBoss JIRA] (JBDS-4681) Fuse examples from central fail to install Fuse tooling from central

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4681?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4681: -------------------------------- Description: Running fuse example wizard from Central fails to install fuse tools from central update site when requested (see attached screen-cast for steps). !fuse-examples-canniot-install-tools.mp4|id=media! was: Running fuse example wizard from Central fails to install fuse tools from central update site when requested (see attached screen-cast for steps). !media.wmv|id=media! > Fuse examples from central fail to install Fuse tooling from central > -------------------------------------------------------------------- > > Key: JBDS-4681 > URL: https://issues.jboss.org/browse/JBDS-4681 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 11.2.0.GA > Environment: Windows 10 Pro 64-bit > Reporter: Denis Golovin > Attachments: fuse-examples-canniot-install-tools.mp4 > > > Running fuse example wizard from Central fails to install fuse tools from central update site when requested (see attached screen-cast for steps). > !fuse-examples-canniot-install-tools.mp4|id=media! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4681) Fuse examples from central fail to install Fuse tooling from central

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4681: ----------------------------------- Summary: Fuse examples from central fail to install Fuse tooling from central Key: JBDS-4681 URL: https://issues.jboss.org/browse/JBDS-4681 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: central Affects Versions: 11.2.0.GA Environment: Windows 10 Pro 64-bit Reporter: Denis Golovin Attachments: fuse-examples-canniot-install-tools.mp4 Running fuse example wizard from Central fails to install fuse tools from central update site when requested (see attached screen-cast for steps). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

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

by Dhiraj Bokde (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ] Dhiraj Bokde commented on JBIDE-25700: -------------------------------------- Is it just a matter of changing all file permissions (after archive extraction) to allow {{root}} group to read/write? I think that should fix it. > 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)

7 years, 10 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25759: ------------------------------------- Summary: CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes (was: CDK Server adapter editor: layout glitches for "--skip-(un)registration"-checkbox) > CDK Server adapter editor: layout and labelling glitches for "--skip-(un)registration"-checkboxes > ------------------------------------------------------------------------------------------------- > > 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 > Assignee: Rob Stryker > 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: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25759: ------------------------------------- Description: 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: !screenshot-1.png! And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . was: 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: > 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: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25759: ---------------------------------------- Assignee: Rob Stryker > 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 > Assignee: Rob Stryker > 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: > !screenshot-1.png! > And then one could wonder if simply using "skip registration when starting" and "skip unregistration when stopping" are more easily understood than "add --skip-registration flag when starting" and "add --skip-unregistration flag when stopping" . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25759?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25759: ------------------------------------- Attachment: screenshot-1.png > 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)

7 years, 10 months

1
0
0 / 0

[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)

7 years, 10 months

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)

7 years, 10 months

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)

7 years, 10 months

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