Bug 969048 - Missing env variable OPENSHIFT_JBOSSEAP_PORT
Missing env variable OPENSHIFT_JBOSSEAP_PORT
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Jason DeTiberus
libra bugs
Depends On:
  Show dependency treegraph
Reported: 2013-05-30 10:40 EDT by Chris Ryan
Modified: 2013-05-31 04:57 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-05-30 13:43:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Chris Ryan 2013-05-30 10:40:53 EDT
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:

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

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 13:43:48 EDT

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 04:57:19 EDT
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.