May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25700: ------------------------------- Sprint: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018, devex #150 June 2019 (was: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018) > Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK) > -------------------------------------------------------------------------------------------------------------------- > > 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 > Labels: server_adapter, springboot > Fix For: 4.6.0.AM3 > > Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png > > > 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)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25905) [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25905?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25905: ------------------------------- Sprint: devex #149 May 2018, devex #150 June 2019 (was: devex #149 May 2018) > [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25905 > URL: https://issues.jboss.org/browse/JBIDE-25905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.6.0.AM3 > > Attachments: service-ports.gif, services-routing-page-no-labels.png, services-routing-page.png > > > [Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard. > Service Ports table starts to behave awkward after reset. > steps: > # ASSERT: have a docker image available that exposes several ports (ex. registry.access.redhat.com/openshift3/ose-haproxy-router:v3.7.14 which exposes 4 ports) > # EXEC: in Docker Explorer: select your docker image and pick "Deploy to OpenShift..." from the context menu > # ASSERT: "Deploy Image to OpenShift" wizard shows up > # EXEC: get to the "Services & Routing Settings" page > # ASSERT: all ports are listed, a port is checked in column "Used by route" > !services-routing-page.png! > # EXEC: hit "Reset" (and confirm the dialog that asks you if you want to reset the ports) > # EXEC: click in the column "Used by route" on the 2nd port (or any unchecked entry) > Result: > Labels for columns "Name", "Service Port", "Pod Port" disappear > !services-routing-page-no-labels.png! > !service-ports.gif! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25109: ------------------------------- Sprint: devex #149 May 2018, devex #150 June 2019 (was: devex #149 May 2018) > Server adapter editor: provide ability to only change debug port (and not the debug port key) > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25109 > URL: https://issues.jboss.org/browse/JBIDE-25109 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: openshift_v3, server_adapter_editor > Fix For: 4.6.x > > > Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25553: ------------------------------- Sprint: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018, devex #150 June 2019 (was: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018) > Cannot create Hibernate Console Configuration for projects with java 9 > ---------------------------------------------------------------------- > > Key: JBIDE-25553 > URL: https://issues.jboss.org/browse/JBIDE-25553 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.2.AM2 > Reporter: Rastislav Wagner > Assignee: Koen Aers > Priority: Critical > Fix For: 4.6.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25586: ------------------------------- Sprint: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018, devex #150 June 2019 (was: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018) > OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK > ---------------------------------------------------------------- > > Key: JBIDE-25586 > URL: https://issues.jboss.org/browse/JBIDE-25586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.2.Final > Environment: FC27 > OpenJDK 9.0.1 > CDK v3.3.0-rc.1-1 > eclipse.buildId=11.2.0.GA-v20180115-0516-B1866 > java.version=9.0.1 > 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: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > Reporter: Josef Kopriva > Assignee: Rob Stryker > Priority: Critical > Labels: cdk, connection > Fix For: 4.6.0.AM2 > > > But, connecting to online openshift instance works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25838: ------------------------------- Sprint: devex #149 May 2018, devex #150 June 2019 (was: devex #149 May 2018) > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: connection, explorer > Fix For: 4.6.0.AM2 > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25916) OpenShift Server Adapter: Error in Log after "Restart in Debug"

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25916?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25916: ------------------------------- Sprint: devex #148 April 2018, devex #149 May 2018, devex #150 June 2019 (was: devex #148 April 2018, devex #149 May 2018) > OpenShift Server Adapter: Error in Log after "Restart in Debug" > --------------------------------------------------------------- > > Key: JBIDE-25916 > URL: https://issues.jboss.org/browse/JBIDE-25916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.Final > Environment: F28 + Red Hat JBoss Developer Studio Build id: GA-v20180410-1152-B2341 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Critical > Labels: debugging, server_adapter > Fix For: 4.6.0.AM2 > > Attachments: error-launching-server.png > > > An error occurs when restarting server adapter in debug: > {code:java} > eclipse.buildId=11.3.0.GA-v20180410-1152-B2341 > java.version=1.8.0_162 > 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/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Warning > Wed Apr 11 18:09:03 CEST 2018 > Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy > org.eclipse.core.runtime.CoreException: Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy > at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.handleSyncDownFailure(OpenShiftPublishController.java:92) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:61) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182) > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1340) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$1.run(OpenShiftLaunchController.java:261) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Contains: Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war > rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3] > error: exit status 23 > {code} > {code:java} > eclipse.buildId=11.3.0.GA-v20180410-1152-B2341 > java.version=1.8.0_162 > 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/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Apr 11 18:09:03 CEST 2018 > Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy > {code} > {code:java} > eclipse.buildId=11.3.0.GA-v20180410-1152-B2341 > java.version=1.8.0_162 > 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/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Apr 11 18:09:03 CEST 2018 > Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war > rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3] > error: exit status 23 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26012) OpenShift New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26012?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26012. ------------------------------ Resolution: Done > OpenShift New and Noteworthy for 4.6.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26012 > URL: https://issues.jboss.org/browse/JBIDE-26012 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM2 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for OpenShift 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26007) Fuse Tools New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26007?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26007. ------------------------------ Resolution: Done > Fuse Tools New and Noteworthy for 4.6.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26007 > URL: https://issues.jboss.org/browse/JBIDE-26007 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Critical > Labels: task > Fix For: 4.6.0.AM2 > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25999 #comment Create N&N for Fuse Tools 4.6.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Fuse Tools for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25999) Create New and Noteworthy for 4.6.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25999?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25999. ------------------------------ Resolution: Done > Create New and Noteworthy for 4.6.0.AM2 > --------------------------------------- > > Key: JBIDE-25999 > URL: https://issues.jboss.org/browse/JBIDE-25999 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.6.0.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2018