[JBoss JIRA] (JBIDE-25547) Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25547?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-25547.
---------------------------------
Resolution: Done
commit edf4c841e9c07db329b26a5561f0eb13215ba6fa
Author: Rob Stryker <rob(a)oxbeef.net>
Date: Wed Jan 17 16:23:43 2018 -0500
This commit solved this issue and added the workspace setting hyperlink.
> Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25547
> URL: https://issues.jboss.org/browse/JBIDE-25547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
> Attachments: connection-wizard.png
>
>
> # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location
> # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid
> (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc)
> # EXEC: launch connection wizard
> # EXEC: provide server url and authentication means
> # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area
> !connection-wizard.png!
> Result:
> You cannot save your connection unless you override the oc location for this connection. In order to correct the preferences you have to cancel the wizard and go to the preferences. Once you correct the value in preferences, you are not prevented from saving the connection any more.
> Expected result:
> Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25549) Cannot create OpenShift connection with OC binary on path
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25549?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25549:
--------------------------------
Fix Version/s: 4.5.3.AM3
(was: 4.5.x)
> Cannot create OpenShift connection with OC binary on path
> ---------------------------------------------------------
>
> Key: JBIDE-25549
> URL: https://issues.jboss.org/browse/JBIDE-25549
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Environment: FC27
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
> Attachments: image-2018-01-09-08-50-39-566.png, image-2018-01-09-08-53-21-234.png
>
>
> I have OC Binary on path:
> !image-2018-01-09-08-50-39-566.png|thumbnail!
> But when I try to create OpenShift connection, wizard is showing an error message, that OC binary is not set:
> !image-2018-01-09-08-53-21-234.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25547) Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25547?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25547:
--------------------------------
Fix Version/s: 4.5.3.AM3
(was: 4.5.x)
> Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25547
> URL: https://issues.jboss.org/browse/JBIDE-25547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
> Attachments: connection-wizard.png
>
>
> # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location
> # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid
> (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc)
> # EXEC: launch connection wizard
> # EXEC: provide server url and authentication means
> # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area
> !connection-wizard.png!
> Result:
> You cannot save your connection unless you override the oc location for this connection. In order to correct the preferences you have to cancel the wizard and go to the preferences. Once you correct the value in preferences, you are not prevented from saving the connection any more.
> Expected result:
> Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online
by Dhiraj Bokde (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Dhiraj Bokde commented on JBIDE-25700:
--------------------------------------
[~adietish], I've merge the upstream fix including a fix for karaf images. Please pull and try to build the image again.
> 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)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online
by Dhiraj Bokde (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Dhiraj Bokde commented on JBIDE-25700:
--------------------------------------
[~adietish], there is an open PR for this issue https://github.com/fabric8io-images/s2i/pull/114.
[~rhuss], it looks good to me, can you review it as well?
> 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)
7 years, 11 months