Bug 969048 - Missing env variable OPENSHIFT_JBOSSEAP_PORT
Summary: Missing env variable OPENSHIFT_JBOSSEAP_PORT
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 1.2.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jason DeTiberus
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-30 14:40 UTC by Chris Ryan
Modified: 2013-05-31 08:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-30 17:43:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Environment variable output (2.48 KB, text/plain)
2013-05-30 14:40 UTC, Chris Ryan
no flags Details

Description Chris Ryan 2013-05-30 14:40:53 UTC
Created attachment 754899 [details]
Environment variable output

Description of problem:
After creating a jbosseap app, the OPENSHIFT_JBOSSEAP_PORT env variable is missing.

Version-Release number of selected component (if applicable):
ec2_ami_id => ami-c34a20aa
On-premise openshift-origin-broker 1.5.2

How reproducible:
Always

Steps to Reproduce:
1. Create jbosseap app
2. SSH into gear, run 'env' command
3.

Actual results:
OPENSHIFT_JBOSSEAP_PORT env variable is not present

Expected results:
OPENSHIFT_JBOSSEAP_PORT env variable should be present

Additional info:
Please see the attached output.

Comment 2 Jason DeTiberus 2013-05-30 17:43:48 UTC
Chris,

With the switch to the v2 cart spec, the environment variable has changed from OPENSHIFT_JBOSSEAP_PORT to OPENSHIFT_JBOSSEAP_HTTP_PORT.

v1 to v2 migrations will maintain the old variable, but new v2 carts will only have the new variable.

Comment 3 Chris Ryan 2013-05-31 08:57:19 UTC
Hi Jason,

Thanks for the heads up, I'll change our test cases accordingly.


Note You need to log in before you can comment on or make changes to this bug.