Bug 992897

Description of problem:
Given a scaling app, if adding only one or two DB carts to this app, the port(s) of the added DB cart(s) will be missing. However, if adding all the three DB carts to this app (say, MySQL-5.1, MongoDB-2.2, Postgresql-8.4(Postgresql-9.2)), only the port of the lastly added one will be at presence. One of the consequences is that, port-forward is not functioning if adding only one (even two) DB carts to a scaling app.

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

How reproducible:
always

Steps to Reproduce:
1. create a scaling app
2. add one db cart to this app (e.g., mysql-5.1)
3. SSH into this app, and check the port of the added DB cart.
4. add another db cart to this app (e.g., mongodb-2.2)
5. repeat Step 3
6. add a third db cart to this app (e.g., postgresql-8.4)
7. repeat Step 3
8. forward the app's ports to local

Actual results:
In Step 3 and 5, the ports of the first two DB carts were missing. However, in Step 7, the port of the lastly added DB carts was at presence. If shuffling the order of adding the three DB carts, the results are similar, i.e., only the port of the lastly DB cart is not null.

[sphp-zwstg.stg.rhcloud.com 51ff09dd2587c84886000087]\> env | grep DB_PORT
OPENSHIFT_MYSQL_DB_PORT=
OPENSHIFT_MONGODB_DB_PORT=
OPENSHIFT_POSTGRESQL_DB_PORT=47701

Moreover, forwarding all the DB ports to local did not function for the first two added DB carts:

Service    Local                OpenShift
---------- --------------- ---- ----------------------------------------------------
haproxy    127.0.0.1:8080   =>  127.13.123.130:8080
haproxy    127.0.0.1:8081   =>  127.13.123.131:8080
httpd      127.0.0.1:8082   =>  127.13.123.129:8080
postgresql 127.0.0.1:47701  =>  51ff0b8ddbd93cc62c00023c-zwstg.stg.rhcloud.com:47701

Expected results:
All the DB ports of a scaling app should not be null regardless of the number of DB carts added to this app.

Additional info: