Description of problem: If trying to show a scalable app with multiple gears scaled-up, the scaled-up gear would be listed with haproxy together as below: rhc app show app123 --gears ID State Cartridges Size SSH URL ------------------------ ------- --------------------- ----- -------------------------------------------------------------------------- 5199e6fa990e977f6e000004 started perl-5.10 haproxy-1.4 small 5199e6fa990e977f6e000004.rhcloud.com 5199e7ad990e977f6e000005 started perl-5.10 haproxy-1.4 small 5199e7ad990e977f6e000005.rhcloud.com 115508612461076619984896 started perl-5.10 haproxy-1.4 small 115508612461076619984896.rhcloud.com 334722207534562479702016 started perl-5.10 haproxy-1.4 small 334722207534562479702016.rhcloud.com Version-Release number of selected component (if applicable): devenv_3247 rhc-1.9.2.gem How reproducible: always Steps to Reproduce: 1.Creat a scalable app and scale-up a few times. 2.Run rhc app show -a appname --gears Actual results: The haproxy gear is returned with every scaled-up web gear as pasted in description. Expected results: The haproxy gear should not be returned with scaled-up web gear together as below: #rhc app show app123 --gears ID State Cartridges Size SSH URL ------------------------ ------- --------------------- ----- -------------------------------------------------------------------------- 5199e6fa990e977f6e000004 started perl-5.10 haproxy-1.4 small 5199e6fa990e977f6e000004.rhcloud.com 5199e7ad990e977f6e000005 started perl-5.10 small 5199e7ad990e977f6e000005.rhcloud.com 115508612461076619984896 started perl-5.10 small 115508612461076619984896.rhcloud.com 334722207534562479702016 started perl-5.10 small 334722207534562479702016.rhcloud.com Additional info:
This is a consequence of a design decision we made for colocation. Eventually, all web gears will be capable of having haproxy, and haproxy will be activated as necessary. We'll iterate on the current presentation at that point.