Bug 810349

Summary:	create .env/OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT for non-scaled apps
Product:	OKD	Reporter:	Bill DeCoste <wdecoste>
Component:	Pod	Assignee:	Bill DeCoste <wdecoste>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.x	CC:	rmillner, xtian
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-13 18:33:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bill DeCoste 2012-04-05 16:49:39 UTC

Description of problem:
OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT doesn't exist for non-scaled apps

Version-Release number of selected component (if applicable):


How reproducible:
100%


Steps to Reproduce:
1. Create non-scaled JBoss app
2.
3.
  
Actual results:
OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT does not exist


Expected results:
OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT should exist and use port 7600


Additional info:

Comment 1 Xiaoli Tian 2012-04-06 08:12:05 UTC

The fix has not been included in devenv_1696, need to wait for the new build comes.

Comment 2 Xiaoli Tian 2012-04-09 03:35:41 UTC

Verified it on devenv_1697 with cartridge-jbossas-7-0.90.2-1.git.119.b643636.el6.noarch.


[jbossapp3-domx85.dev.rhcloud.com .env]\> cat OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT 
export OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT='7600'

Comment 3 Rob Millner 2012-04-10 18:04:03 UTC

If scaling is ever enabled on that gear, then OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT will be overwritten with the proxy port (ex: 35531).  Does 7600 need to be stored in a different variable?  OPENSHIFT_JBOSS_CLUSTER_PORT?