Bug 1204207

Summary: Exposed haproxy-sni-proxy mapped ports not set in the install script
Product: OpenShift Online Reporter: Hiram Chirino <hchirino>
Component: ImageAssignee: Ben Parees <bparees>
Status: CLOSED WONTFIX QA Contact: libra bugs <libra-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.xCC: bperkins, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-23 21:32:05 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 Hiram Chirino 2015-03-20 15:31:21 UTC 
Description of problem:
BZ 1144788 addressed the issue of exposing the TLS port mapping as env vars.  
But it only sets those vars in the control script, not the install script.
Comment 1 Ben Parees 2015-03-20 15:39:15 UTC 
https://issues.jboss.org/browse/ENTESB-1952
Comment 2 Ben Parees 2015-03-20 22:29:41 UTC 
I think this is fundamentally impossible for us given our current goals...  the flow of gear creation is:
1) run install/setup steps
2) connect the gear to the external router

it's at step 2 that the ports are assigned/identified for TLS (among other things), so we can't set the env variables until then without a major reworking.
Comment 3 Hiram Chirino 2015-03-23 21:58:16 UTC 
The TLS ports for a node are static.  How hard can this be?
Comment 4 JBoss JIRA Server 2015-03-24 20:54:14 UTC 
Hiram Chirino <hiram> updated the status of jira ENTESB-1952 to Resolved
Comment 5 JBoss JIRA Server 2015-04-03 15:38:26 UTC 
Marek Schmidt <maschmid> updated the status of jira ENTESB-1952 to Closed