[JBoss JIRA] (JBIDE-23152) NPE when deploying image with ENV with no value
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23152?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23152:
-------------------------------
Description:
EXEC: first deploy jboss-eap64-openshift builder image
ASSERT: wait until deployment is finished
EXEC: delete the deployment
EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd)
ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=)
was:
EXEC: first deploy jboss-eap64-openshift
ASSERT: wait until deployment is finished
EXEC: delete the deployment
EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd)
ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=)
> NPE when deploying image with ENV with no value
> -----------------------------------------------
>
> Key: JBIDE-23152
> URL: https://issues.jboss.org/browse/JBIDE-23152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Labels: openshift, openshift_v3
> Fix For: 4.4.2.AM2
>
>
> EXEC: first deploy jboss-eap64-openshift builder image
> ASSERT: wait until deployment is finished
> EXEC: delete the deployment
> EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd)
> ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23014) Allow connections to configure the cluster namespace from which to get clusterwide templates
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23014?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23014:
-------------------------------
Labels: connection connection_wizard new_and_noteworthy openshift openshift_v3 (was: connection connection_wizard openshift_v3)
Affects Version/s: 4.4.1.Final
> Allow connections to configure the cluster namespace from which to get clusterwide templates
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23014
> URL: https://issues.jboss.org/browse/JBIDE-23014
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Jeff Cantrill
> Assignee: Jeff MAURY
> Labels: connection, connection_wizard, new_and_noteworthy, openshift, openshift_v3
> Fix For: 4.4.2.AM1
>
>
> There are a few places where we assume the cluster is configured with the openshift namespace (e.gretrieve templates) which contains templates and other resources that are available to everyone. We should provide a per connection configuration (advanced property?) that allows us to change the default since it is not discoverable from the server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23015:
-------------------------------
Labels: new_and_noteworthy openshift openshift_v3 (was: )
> Creating a route should have a default port
> -------------------------------------------
>
> Key: JBIDE-23015
> URL: https://issues.jboss.org/browse/JBIDE-23015
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift, openshift_v3
> Fix For: 4.4.2.AM1
>
>
> When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail.
> There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others.
> The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation)
> To reproduce:
> - git clone https://github.com/redhat-helloworld-msa/aloha
> - mvn package
> - build docker image from Dockerfile, to CDK docker connection
> - deploy docker image to openshift
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22640:
-------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.1.Final)
Affects Version/s: 4.4.1.Final
> Server Adapter Editor: Update to Openshift server adapter is not saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-22640
> URL: https://issues.jboss.org/browse/JBIDE-22640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final, 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.2.AM2
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: the connection filed is blank
> EXEC: using the dropdown change the connection
> ASSERT: the dirty flag of the server editor is not set
> EXEC: close the server editor
> EXEC: open the server editor again
> ASSERT: the connection field is still blank
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months