[JBoss JIRA] (JBDS-4715) Why does installer jar contain 12.9.0.a.jre.javase, config.a.jre.javase, AM1-v20180717-0127-B3012 as the version?
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4715?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-4715.
-------------------------------
Verified yesterday in build 3027. All if fine now.
> Why does installer jar contain 12.9.0.a.jre.javase,config.a.jre.javase,AM1-v20180717-0127-B3012 as the version?
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4715
> URL: https://issues.jboss.org/browse/JBDS-4715
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.9.0.AM1
> Environment: F28
> devstudio-12.9.0.a.jre.javase,config.a.jre.javase,AM1-v20180717-0127-B3012-installer-standalone.jar
> openjdk version "1.8.0_172"
> OpenJDK Runtime Environment (build 1.8.0_172-b11)
> OpenJDK 64-Bit Server VM (build 25.172-b11, mixed mode)
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 12.9.0.AM1
>
> Attachments: image-2018-07-17-07-27-26-379.png
>
>
> I was not able to to finish jar installer, it ends with error window:
> !image-2018-07-17-07-27-26-379.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26204:
------------------------------------------
This is included in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1774] for JBIDE-25700
> Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26204
> URL: https://issues.jboss.org/browse/JBIDE-26204
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.9.0.AM1
>
> Attachments: pod-log-console-empty.png, port-forwarding-stopped.png
>
>
> * Setup:
> *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700
> *# ASSERT: make sure you have an app with a pod running in OpenShift
> *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc")
> * Port Log:
> *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..."
> *# Result:
> The "Console" view shows up but nothing happens, there's no output.
> !pod-log-console-empty.png!
> * Port Forwarding:
> *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..."
> *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped"
> *# EXEC: hit "Start All" button
> *# Result:
> Port forwarding is not started, the "Status" column for the ports stays "Stopped"
> !port-forwarding-stopped.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26204:
-------------------------------------
Git Pull Request: (was: https://github.com/jbosstools/jbosstools-openshift/pull/1774)
> Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26204
> URL: https://issues.jboss.org/browse/JBIDE-26204
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.9.0.AM1
>
> Attachments: pod-log-console-empty.png, port-forwarding-stopped.png
>
>
> * Setup:
> *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700
> *# ASSERT: make sure you have an app with a pod running in OpenShift
> *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc")
> * Port Log:
> *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..."
> *# Result:
> The "Console" view shows up but nothing happens, there's no output.
> !pod-log-console-empty.png!
> * Port Forwarding:
> *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..."
> *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped"
> *# EXEC: hit "Start All" button
> *# Result:
> Port forwarding is not started, the "Status" column for the ports stays "Stopped"
> !port-forwarding-stopped.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25700:
-------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1705, https://github.com/fabric8io-images/s2i/pull/124, https://github.com/jbosstools/jbosstools-openshift/pull/1765, https://github.com/fabric8io-images/s2i/pull/130, https://github.com/jbosstools/jbosstools-openshift/pull/1774 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1705, https://github.com/fabric8io-images/s2i/pull/124, https://github.com/jbosstools/jbosstools-openshift/pull/1765, https://github.com/fabric8io-images/s2i/pull/130, https://github.com/jbosstools/jbosstools-openshift/pull/1772)
> 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, upstream
> Fix For: 4.9.0.AM1
>
> 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)
7 years, 8 months