Description of problem: Setting scales_from or scales_to beyond the current_scale number of a cartridge of a scalable app renders the auto-scaler in haproxy cartridge with incorrect information. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. On a scalable php app with 2 php gears, set the scales_from to 4 2. Add mysql/or scaleup once (this will increase the php gears to 4) 3. Now check the logs... haproxy auto-scaler keeps sending scale-down requests. The requests get turned down alright but clearly indicates that the haproxy cartridge has not gotten the new min/max for the php cartridge. Actual results: Haproxy sends useless scaledown requests Expected results: Haproxy should not send useless scaledown requests Additional info:
Fixed with rev#cb8dbc6bbc2014f319239724d035470ffa30ae13 in origin-server/master
Checked on devenv_2377, after scale-up the app to the set scaled_from value. No scale-down requests found in scale_events.log