[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 edited comment on JBIDE-25700 at 2/27/18 10:04 AM:
--------------------------------------------------------------------
[~aurelien.pupier] just tried with the wildfly sample that's available on https://console.starter-us-east-1.openshift.com and it works fine.
Files are owned by default/root but files created by oc rsync are owned by an unknown user beloging to the root group
{code}
drwxrwxr-x. 3 default root 4096 Feb 27 14:12 configuration
drwxr-xr-x. 6 1113880000 root 84 Feb 27 14:12 data
drwxrwxr-x. 3 default root 81 Feb 27 14:28 deployments
drwxrwxr-x. 3 default root 17 Jan 29 2016 lib
drwxr-xr-x. 2 1113880000 root 24 Feb 27 14:11 log
drwxrwxr-x. 5 default root 67 Feb 27 14:12 tmp
{code}
There are not permission issue though. I can get into the pod
{code}
oc rsh <pod>
{code}
and create a new file via touch
{code}
/wildfly/standalone/deployments
sh-4.2$ touch test
sh-4.2$ ls -l
total 16
-rw-rw-r--. 1 default root 8870 Jan 29 2016 README.txt
drwxr-xr-x. 5 1113880000 root 86 Feb 27 14:12 ROOT.war
-rw-r--r--. 1 1113880000 root 8 Feb 27 14:12 ROOT.war.deployed
-rw-r--r--. 1 1113880000 root 0 Feb 27 15:00 test
sh-4.2$
{code}
When trying the same thing with a pod for the fuse-on-openshift example (that I initially deploy via the fabric8 maven plugin, using the *fabric8/s2i-java* base image), I hit a permission error (*touch: cannot touch 'test.txt': Permission denied*):
{code}
sh-4.2$ pwd
/deployments/BOOT-INF/classes
sh-4.2$ touch test.txt
touch: cannot touch 'test.txt': Permission denied
sh-4.2$ ls -l
total 8
-rw-r--r--. 1 jboss root 547 Feb 27 14:41 application.properties
-rw-r--r--. 1 jboss root 468 Feb 27 14:41 logback.xml
drwxr-xr-x. 3 jboss root 23 Feb 27 14:41 org
drwxr-xr-x. 2 jboss root 31 Feb 27 14:41 spring
{code}
was (Author: adietish):
[~aurelien.pupier] just tried with the wildfly sample that's available on https://console.starter-us-east-1.openshift.com and it works fine.
Files are owned by default/root but files created by oc rsync are owned by an unknown user beloging to the root group
{code}
drwxrwxr-x. 3 default root 4096 Feb 27 14:12 configuration
drwxr-xr-x. 6 1113880000 root 84 Feb 27 14:12 data
drwxrwxr-x. 3 default root 81 Feb 27 14:28 deployments
drwxrwxr-x. 3 default root 17 Jan 29 2016 lib
drwxr-xr-x. 2 1113880000 root 24 Feb 27 14:11 log
drwxrwxr-x. 5 default root 67 Feb 27 14:12 tmp
{code}
There are not permission issue though. I can get into the pod
{code}
oc rsh <pod>
{code}
and create a new file via touch
{code}
/wildfly/standalone/deployments
sh-4.2$ touch test
sh-4.2$ ls -l
total 16
-rw-rw-r--. 1 default root 8870 Jan 29 2016 README.txt
drwxr-xr-x. 5 1113880000 root 86 Feb 27 14:12 ROOT.war
-rw-r--r--. 1 1113880000 root 8 Feb 27 14:12 ROOT.war.deployed
-rw-r--r--. 1 1113880000 root 0 Feb 27 15:00 test
sh-4.2$
{code}
When trying the same thing with a pod for the fuse-on-openshift example (that I initially deploy via the fabric8 maven plugin, using the *fabric8/s2i-java* base image), I hit a permission error:
{code}
sh-4.2$ pwd
/deployments/BOOT-INF/classes
sh-4.2$ touch test.txt
touch: cannot touch 'test.txt': Permission denied
sh-4.2$ ls -l
total 8
-rw-r--r--. 1 jboss root 547 Feb 27 14:41 application.properties
-rw-r--r--. 1 jboss root 468 Feb 27 14:41 logback.xml
drwxr-xr-x. 3 jboss root 23 Feb 27 14:41 org
drwxr-xr-x. 2 jboss root 31 Feb 27 14:41 spring
{code}
> 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.AM2
>
>
> 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
[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 edited comment on JBIDE-25700 at 2/27/18 10:03 AM:
--------------------------------------------------------------------
[~aurelien.pupier] just tried with the wildfly sample that's available on https://console.starter-us-east-1.openshift.com and it works fine.
Files are owned by default/root but files created by oc rsync are owned by an unknown user beloging to the root group
{code}
drwxrwxr-x. 3 default root 4096 Feb 27 14:12 configuration
drwxr-xr-x. 6 1113880000 root 84 Feb 27 14:12 data
drwxrwxr-x. 3 default root 81 Feb 27 14:28 deployments
drwxrwxr-x. 3 default root 17 Jan 29 2016 lib
drwxr-xr-x. 2 1113880000 root 24 Feb 27 14:11 log
drwxrwxr-x. 5 default root 67 Feb 27 14:12 tmp
{code}
There are not permission issue though. I can get into the pod
{code}
oc rsh <pod>
{code}
and create a new file via touch
{code}
/wildfly/standalone/deployments
sh-4.2$ touch test
sh-4.2$ ls -l
total 16
-rw-rw-r--. 1 default root 8870 Jan 29 2016 README.txt
drwxr-xr-x. 5 1113880000 root 86 Feb 27 14:12 ROOT.war
-rw-r--r--. 1 1113880000 root 8 Feb 27 14:12 ROOT.war.deployed
-rw-r--r--. 1 1113880000 root 0 Feb 27 15:00 test
sh-4.2$
{code}
When trying the same thing with a pod for the fuse-on-openshift example (that I initially deploy via the fabric8 maven plugin, using the *fabric8/s2i-java* base image), I hit a permission error:
{code}
sh-4.2$ pwd
/deployments/BOOT-INF/classes
sh-4.2$ touch test.txt
touch: cannot touch 'test.txt': Permission denied
sh-4.2$ ls -l
total 8
-rw-r--r--. 1 jboss root 547 Feb 27 14:41 application.properties
-rw-r--r--. 1 jboss root 468 Feb 27 14:41 logback.xml
drwxr-xr-x. 3 jboss root 23 Feb 27 14:41 org
drwxr-xr-x. 2 jboss root 31 Feb 27 14:41 spring
{code}
was (Author: adietish):
[~aurelien.pupier] just tried with the wildfly sample that's available on https://console.starter-us-east-1.openshift.com and it works fine.
Files are owned by default/root but files created by oc rsync are owned by an unknown user beloging to the root group
{code}
drwxrwxr-x. 3 default root 4096 Feb 27 14:12 configuration
drwxr-xr-x. 6 1113880000 root 84 Feb 27 14:12 data
drwxrwxr-x. 3 default root 81 Feb 27 14:28 deployments
drwxrwxr-x. 3 default root 17 Jan 29 2016 lib
drwxr-xr-x. 2 1113880000 root 24 Feb 27 14:11 log
drwxrwxr-x. 5 default root 67 Feb 27 14:12 tmp
{code}
> 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.AM2
>
>
> 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
[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:
------------------------------------------
[~aurelien.pupier] just tried with the wildfly sample that's available on https://console.starter-us-east-1.openshift.com and it works fine.
Files are owned by default/root but files created by oc rsync are owned by an unknown user beloging to the root group
{code}
drwxrwxr-x. 3 default root 4096 Feb 27 14:12 configuration
drwxr-xr-x. 6 1113880000 root 84 Feb 27 14:12 data
drwxrwxr-x. 3 default root 81 Feb 27 14:28 deployments
drwxrwxr-x. 3 default root 17 Jan 29 2016 lib
drwxr-xr-x. 2 1113880000 root 24 Feb 27 14:11 log
drwxrwxr-x. 5 default root 67 Feb 27 14:12 tmp
{code}
> 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.AM2
>
>
> 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
[JBoss JIRA] (JBIDE-25750) fix-versions pulls wrong versions of IUs from wtp repo when updating .target file
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25750?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25750:
-------------------------------
Fix Version/s: 4.5.3.AM3
(was: 4.5.3.AM2)
> fix-versions pulls wrong versions of IUs from wtp repo when updating .target file
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-25750
> URL: https://issues.jboss.org/browse/JBIDE-25750
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.5.3.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM3
>
>
> For 4.71.x, using tychoVersion=1.1.0 and jbossTychoPluginsVersion=1.1.0-SNAPSHOT in the root pom of jbosstools-target-platforms, I can validate and mirror the TP locally.
> For 4.72.x, same thing.
> But for 4.73.x, I get incorrect versions of the wtp feature.groups.
> {code}
> + <unit id="org.eclipse.jst.enterprise_ui.feature.feature.group" version="3.9.2.v201802222200"/>
> + <unit id="org.eclipse.jst.web_core.feature.feature.group" version="3.9.1.v201802222200"/>
> + <unit id="org.eclipse.jst.web_ui.feature.feature.group" version="3.9.0.v201802222200"/>
> + <unit id="org.eclipse.wst.ws_ui.feature.feature.group" version="3.8.1.v201802222200"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development
by Bob Davis (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ]
Bob Davis commented on JBIDE-25736:
-----------------------------------
Thanks everyone - [~nickboldt] - your last comment makes it pretty clear to me, and the data you show on the spreadsheet is pretty compelling (showing that these plugins just are not being used).
So, I'm good with:
Deprecating, remove from default installation (if applicable), & create a Central connector (if not already exist):
* jbosstools-portlet
* jbosstools-aerogear
* jbosstools-browsersim
* jbosstools-livereload
2 projects to remove, since they were deprecated some time ago:
* jbosstools-freemarker
* jbosstools-arquillian
Bob
> deprecate features from JBoss Tools with low usage / low development
> --------------------------------------------------------------------
>
> Key: JBIDE-25736
> URL: https://issues.jboss.org/browse/JBIDE-25736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM2
>
>
> This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
> * jbosstools-portlet
> * jbosstools-aerogear
> * jbosstools-browsersim
> * jbosstools-livereload
> * {color:red}-jbosstools-webservices-{color}
> * {color:red}-jbosstools-javaee-{color}
> * {color:red}-jbosstools-forge-{color}
> These projects could be *removed*, since they were deprecated some time ago:
> * jbosstools-freemarker
> * jbosstools-arquillian
> For supporting arguments, see this doc (RH only, sorry):
> https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25736:
------------------------------------
[~rick_wagner] Yes, if you read through the comments, the {color:red}-red strike-throughs-{color} map to comments from devs or project lead (Jeff) about keeping projects I'd previously though as candidates for deprecation. At this point my suggestion is this:
*4 projects to mark deprecated, remove from default installation (if applicable), & create a Central connector (if not already exist):*
* jbosstools-portlet
* jbosstools-aerogear
* jbosstools-browsersim
* jbosstools-livereload
*2 projects to remove, since they were deprecated some time ago:*
* jbosstools-freemarker
* jbosstools-arquillian
> deprecate features from JBoss Tools with low usage / low development
> --------------------------------------------------------------------
>
> Key: JBIDE-25736
> URL: https://issues.jboss.org/browse/JBIDE-25736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM2
>
>
> This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
> * jbosstools-portlet
> * jbosstools-aerogear
> * jbosstools-browsersim
> * jbosstools-livereload
> * {color:red}-jbosstools-webservices-{color}
> * {color:red}-jbosstools-javaee-{color}
> * {color:red}-jbosstools-forge-{color}
> These projects could be *removed*, since they were deprecated some time ago:
> * jbosstools-freemarker
> * jbosstools-arquillian
> For supporting arguments, see this doc (RH only, sorry):
> https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development
by Rick Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ]
Rick Wagner commented on JBIDE-25736:
-------------------------------------
Thanks for looking for ways to clean up, [~nickboldt].
I hope the 'strike-through' red line for web services means it's been spared. I'd vote to keep that one around. (Justification: We get support cases from customers with SOAP web services. When that's the case, I regularly end up using the web services functionality in DevStudio. I'd assume the customers are doing the same.)
SOAP was pretty big a while back, it's going to have a long tail (like COBOL).
> deprecate features from JBoss Tools with low usage / low development
> --------------------------------------------------------------------
>
> Key: JBIDE-25736
> URL: https://issues.jboss.org/browse/JBIDE-25736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM2
>
>
> This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
> * jbosstools-portlet
> * jbosstools-aerogear
> * jbosstools-browsersim
> * jbosstools-livereload
> * {color:red}-jbosstools-webservices-{color}
> * {color:red}-jbosstools-javaee-{color}
> * {color:red}-jbosstools-forge-{color}
> These projects could be *removed*, since they were deprecated some time ago:
> * jbosstools-freemarker
> * jbosstools-arquillian
> For supporting arguments, see this doc (RH only, sorry):
> https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months