Not clear how hard this is or whether it is a blocker for anything in 2.2. We definitely want to investigate both.

Grzegorz, what's the use case for those env variables?  The value would be one of the frontend SNI ports (eg 2303), but the app isn't going to try to reach itself over that port, so not sure why it needs that information?

Also I think your expected and actual results are reversed?

You need these e.g. for the fabric-cxf-registry, where you can register endpoints for each service, which can be consumed, e.g. by some load balancer, or a client configured to get the actual URL from the fabric by a logical name.

The assigned ports are reported when you create the app, is that sufficient for now?

Ben:
 - right - application doesn't connect to itself via these ports
 - right - I reversed actual and expected (can I edit the description in BZ?)

As Marek said, Fuse is registering endpoints in ZooKeeper which are then used by external clients, which have to know external tls ports. We provide internal "port mapper" which translates internal (bind address + private port) to public (app-domain.host : tls port) addresses of WebServices/REST endpoints.

Ben - what do you mean by "assigned ports are reported"? I though about cartridge notifications, but couldn't find correct example of the event to which cart should be subscribed.

I just meant they are reported to the user during application create.  Though it's possible that same mechanism could be leveraged to get env variables created.

Working on a fix for this here:
https://github.com/openshift/origin-server/pull/5827

(upstream fix is in: https://github.com/openshift/origin-server/pull/5827)

I applied the patch from origin-server and I added:

```
logger.info("REPORTED URLS: #{reported_urls}")
```
before iteration over `reported_urls` and I got the following log:

```
September 23 09:05:50 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [] => [127.13.36.129:8080] with options: {"protocols"=>["http"]}
September 23 09:05:51 INFO Shell command '/usr/sbin/httxt2dbm -f DB -i /etc/httpd/conf.d/openshift/nodes.txt -o /etc/httpd/conf.d/openshift/nodes.db-20140923-25644-1v5r413/new.db' ran. rc=0 out=
September 23 09:05:51 INFO REPORTED URLS: []
September 23 09:05:51 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [TLS_PORT_1] => [127.13.36.129:31314] with options: {"protocols"=>["tls"]}
September 23 09:05:52 INFO REPORTED URLS: []
September 23 09:05:52 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [TLS_PORT_2] => [127.13.36.129:31324] with options: {"protocols"=>["tls"]}
September 23 09:05:53 INFO REPORTED URLS: []
September 23 09:05:53 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [TLS_PORT_3] => [127.13.36.129:31334] with options: {"protocols"=>["tls"]}
September 23 09:05:53 INFO REPORTED URLS: []
September 23 09:05:53 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [TLS_PORT_4] => [127.13.36.129:31344] with options: {"protocols"=>["tls"]}
September 23 09:05:54 INFO REPORTED URLS: []
September 23 09:05:54 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [TLS_PORT_5] => [127.13.36.129:30304] with options: {"protocols"=>["tls"]}
September 23 09:05:54 INFO REPORTED URLS: []
September 23 09:05:54 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [TLS_PORT_6] => [127.13.36.129:4001] with options: {"protocols"=>["tls"]}
September 23 09:05:55 INFO REPORTED URLS: []
September 23 09:05:55 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [TLS_PORT_7] => [127.13.36.129:4002] with options: {"protocols"=>["tls"]}
September 23 09:05:56 INFO REPORTED URLS: []
September 23 09:05:56 INFO Connecting frontend mapping for 54211b80e659c5a57b00000e/fuse: [TLS_PORT_8] => [127.13.36.129:4003] with options: {"protocols"=>["tls"]}
September 23 09:05:56 INFO REPORTED URLS: []
```

The environmental variables for proxy ports were not created... It seems that SNI plugin don't return the reported_urls...

Puddle:
2.1.z/2014-11-05.1

Verify:
Create a fuse application:
[fuse-domainwyy.ose21z-manual.com.cn 545b2bf8db26c8f63f000268]\> env | grep OPENSHIFT_FUSE_APP_TLS_PORT
OPENSHIFT_FUSE_APP_TLS_PORT_1_PROXY_PORT=2308
OPENSHIFT_FUSE_APP_TLS_PORT_3_PROXY_PORT=2310
OPENSHIFT_FUSE_APP_TLS_PORT_1=4001
OPENSHIFT_FUSE_APP_TLS_PORT_3=4003
OPENSHIFT_FUSE_APP_TLS_PORT_2=4002
OPENSHIFT_FUSE_APP_TLS_PORT_2_PROXY_PORT=2309

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2014-1906.html

Hiram Chirino <hiram@hiramchirino.com> updated the status of jira ENTESB-1952 to Resolved

Marek Schmidt <maschmid@redhat.com> updated the status of jira ENTESB-1952 to Reopened

Hiram Chirino <hiram@hiramchirino.com> updated the status of jira ENTESB-1952 to Resolved

Marek Schmidt <maschmid@redhat.com> updated the status of jira ENTESB-1952 to Closed