[JBoss JIRA] (JBIDE-25734) Verify space related issues with oc rsync
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25734?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25734.
---------------------------------
Works as expected in all use cases. Feel free to reopen, if issue occurs.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.AM3
Build id: AM3-v20180320-0313-B2180
> Verify space related issues with oc rsync
> -----------------------------------------
>
> Key: JBIDE-25734
> URL: https://issues.jboss.org/browse/JBIDE-25734
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM1
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: openshift, openshift_v3, rsync, server_adapter
> Fix For: 4.5.3.AM2
>
>
> Check the following use cases:
> - workspace is in a path with space(s)
> - Eclipse project is in a path with space(s)
> - oc binary is in a path with space(s)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-24322.
---------------------------------
Closing.
Retested with Win 10 and Red Hat JBoss Developer Studio Version: 11.3.0.AM3 Build id: AM3-v20180320-0313-B2180.
> Openshift publisher keeps getting more nested
> ---------------------------------------------
>
> Key: JBIDE-24322
> URL: https://issues.jboss.org/browse/JBIDE-24322
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Environment: - OS: Windows 7
> - JbossDev: 10.3.0.0
> - Openshift Client: 3.4
> - Openshift Enterprise: 3.4
> - Workspace location: it's inside a network drive
> Reporter: Rob Stryker
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.4.Final, 4.5.0.AM1
>
>
> During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit.
> We noticed that during the publishing or local change.
>
> The Publish function, always creates a nested deploy directory inside an existing one.
> For instance inside /opt/eap/standalone/deployments/
> 1st Publish:
> deploy/server.war/
> 2nd Publish:
> deploy/deploy/server.war/
> 3nd Publish:
> deploy/deploy/deploy/server.war/
>
> So with 3 publish, you end up with 3 deployed same application.
> This happen also inside the local workspaces for the synchronisation:
> .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift
> The EAP7 images is the jboss-eap70-openshift:latest.
>
> Do you have any idea why this happen?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25700) Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online
by Roland Huß (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Roland Huß commented on JBIDE-25700:
------------------------------------
Hmm, at least the permission in the Dockerfiles look good to me --> https://github.com/fabric8io-images/s2i/blob/66e43a82178744bf3d0e0ddd3b6a...
Could you check how the permissions for the `/deployments` directory is in the image ? For me it looks more like that the process which creates the `BOOT-INF` messes with the permissions. Not sure how this is created though.
Sorry, I got lost a bit in the history of this ticket, but what are the concrete steps I can do to reproduce the issue ?
> 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, 3 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:
------------------------------------------
[~rhuss] ok, cool, please let me know as soon as you you know more/create a new image.
> 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, 3 months
[JBoss JIRA] (JBIDE-25817) Prepare Jenkins labels with flavour capable of running multiple cdk profiles
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25817?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25817 at 3/20/18 3:18 AM:
----------------------------------------------------------------
Added new labels using os images capable of running Devstudio/CDK using better hardware - m1.xlarge flavor, such slaves have 8 CPU, 16GB ram.
Labels:
* rhel716gb
* win10vbox16gb
* win7vbox16gb
* fedora27-xlarge
If required, I can add another labels (fedora, win81, etc...)
was (Author: odockal):
Added new labels using os images capable of running Devstudio/CDK using better hardware - m1.xlarge flavor, such slaves have 8 CPU, 16GB ram.
Labels:
* rhel716gb
* win10vbox16gb
* win7vbox16gb
If required, I can add another labels (fedora, win81, etc...)
> Prepare Jenkins labels with flavour capable of running multiple cdk profiles
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25817
> URL: https://issues.jboss.org/browse/JBIDE-25817
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: qa
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.3.AM3
>
>
> Jenkins label added rhel7-16gb-ram.
> rhel7-x64-jbds-docker openstack image with m1.xlarge flavour set.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25700) Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online
by Roland Huß (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Roland Huß commented on JBIDE-25700:
------------------------------------
The official recommendation by https://docs.openshift.org/latest/creating_images/guidelines.html#openshi... is to use
{code}
RUN chgrp -R 0 /some/directory && \
chmod -R g=u /some/directory
{code}
in the Dockerfile to avoid permission issues (i.e. make the directories group writable). I have to check whether this is true for our images and will fix this, if not.
> 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, 3 months
[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 commented on JBIDE-25303:
------------------------------------------
[~jkopriva] In the CDK but also on OpenShift online I now see the file transfers happening, but there are still permission issues being reported:
{code}
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/application.properties": Operation not permitted (1)
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/logback.xml": Operation not permitted (1)
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/org/mycompany/Application.class": Operation not permitted (1)
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/org/mycompany/MyTransformer.class": Operation not permitted (1)
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/spring/camel-context.xml": Operation not permitted (1)
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52/rsync/main.c(996) [sender=2.6.9]
error: exit status 23
{code}
On the positive side the overall functionality seems to work, files are synced. On the negative side, the initial sync reports an annoying and possibly misleading error.
> 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, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.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, 3 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:
------------------------------------------
[~rhuss] thanks for the update. File transfers now seem to happen but unfortunately I still have permissions issues.
When using the camel-ose-springboot-xml example rsync is complaining about not being able to set permissions:
{code}
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/application.properties": Operation not permitted (1)
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/logback.xml": Operation not permitted (1)
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/org/mycompany/Application.class": Operation not permitted (1)
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/org/mycompany/MyTransformer.class": Operation not permitted (1)
rsync: failed to set permissions on "/deployments/BOOT-INF/classes/spring/camel-context.xml": Operation not permitted (1)
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52/rsync/main.c(996) [sender=2.6.9]
error: exit status 23
{code}
Any idea?
> 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, 3 months