[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 commented on JBIDE-25700:
------------------------------------------
https://github.com/jbosstools/jbosstools-openshift/pull/1765 contains a warning for oc binaries < 3.11 on Linux
> 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.6.0.Final
>
> 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, 5 months
[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25616:
------------------------------------------
[~jkopriva] thx for pointing out!
> [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Labels: docker_image, fis, upstream
> Fix For: 4.9.x
>
> Attachments: java, screenshot-1.png
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> 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)
6 years, 5 months
[JBoss JIRA] (JBIDE-20704) Restore Defaults button in OpenShift 3 preferences does not clear oc location
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20704?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20704:
-------------------------------------
Fix Version/s: 4.6.0.Final
(was: 4.9.x)
> Restore Defaults button in OpenShift 3 preferences does not clear oc location
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20704
> URL: https://issues.jboss.org/browse/JBIDE-20704
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.6.0.Final
>
> Attachments: restore-defaults.gif
>
>
> In Workbench preference dialog on OpenShift 3 preference page the Restore Defaults button should set default values for a property page but if there is an input in text widget for oc location, the value is not cleared. Upon click on Restore Defaults button the text field still contains the same value as before clicking on the button.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-20704) Restore Defaults button in OpenShift 3 preferences does not clear oc location
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20704?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-20704.
--------------------------------------
Assignee: Andre Dietisheim
Resolution: Done
> Restore Defaults button in OpenShift 3 preferences does not clear oc location
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20704
> URL: https://issues.jboss.org/browse/JBIDE-20704
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.6.0.Final
>
> Attachments: restore-defaults.gif
>
>
> In Workbench preference dialog on OpenShift 3 preference page the Restore Defaults button should set default values for a property page but if there is an input in text widget for oc location, the value is not cleared. Upon click on Restore Defaults button the text field still contains the same value as before clicking on the button.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-20704) Restore Defaults button in OpenShift 3 preferences does not clear oc location
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20704?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20704:
-------------------------------------
Sprint: devex #151 June 2018
> Restore Defaults button in OpenShift 3 preferences does not clear oc location
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20704
> URL: https://issues.jboss.org/browse/JBIDE-20704
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.6.0.Final
>
> Attachments: restore-defaults.gif
>
>
> In Workbench preference dialog on OpenShift 3 preference page the Restore Defaults button should set default values for a property page but if there is an input in text widget for oc location, the value is not cleared. Upon click on Restore Defaults button the text field still contains the same value as before clicking on the button.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-20704) Restore Defaults button in OpenShift 3 preferences does not clear oc location
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20704?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20704:
------------------------------------------
I can't reproduce this with the changes in JBIDE-25700, which did quite some refactoring of the preferences page.
Btw. the PR for JBIDE-25700 replaces the dialog with a warning in the preferences page (which is imho superior, one should avoid a dialog on top of another dialog - if possible).
> Restore Defaults button in OpenShift 3 preferences does not clear oc location
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20704
> URL: https://issues.jboss.org/browse/JBIDE-20704
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.9.x
>
> Attachments: restore-defaults.gif
>
>
> In Workbench preference dialog on OpenShift 3 preference page the Restore Defaults button should set default values for a property page but if there is an input in text widget for oc location, the value is not cleared. Upon click on Restore Defaults button the text field still contains the same value as before clicking on the button.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26148:
-------------------------------------
Summary: CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH) (was: CommandLocationBinary: only searches once)
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my PATH while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26148:
-------------------------------------
Description:
[CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
{code:title=CommandLocationBinary}
public String findLocation(int timeout) {
if (foundLoc != null || searchFailed)
return foundLoc;
String searched = CommandLocationLookupStrategy.get().search(this, timeout);
if (searched == null) {
searchFailed = true;
}
foundLoc = searched;
return searched;
}
{code}
Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
What if I update my PATH while I keep Eclipse running?
I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
was:
[CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
{code:title=CommandLocationBinary}
public String findLocation(int timeout) {
if (foundLoc != null || searchFailed)
return foundLoc;
String searched = CommandLocationLookupStrategy.get().search(this, timeout);
if (searched == null) {
searchFailed = true;
}
foundLoc = searched;
return searched;
}
{code}
Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
What if I update my PATH while I keep Eclipse running?
> CommandLocationBinary: only searches once
> -----------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my PATH while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26148:
-------------------------------------
Description:
[CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
{code:title=CommandLocationBinary}
public String findLocation(int timeout) {
if (foundLoc != null || searchFailed)
return foundLoc;
String searched = CommandLocationLookupStrategy.get().search(this, timeout);
if (searched == null) {
searchFailed = true;
}
foundLoc = searched;
return searched;
}
{code}
Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
What if I update my PATH while I keep Eclipse running?
was:
[CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command. But it'll only do so once:
{code:title=CommandLocationBinary}
public String findLocation(int timeout) {
if (foundLoc != null || searchFailed)
return foundLoc;
String searched = CommandLocationLookupStrategy.get().search(this, timeout);
if (searched == null) {
searchFailed = true;
}
foundLoc = searched;
return searched;
}
{code}
Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
What if I update my PATH while I keep Eclipse running?
> CommandLocationBinary: only searches once
> -----------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my PATH while I keep Eclipse running?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months