Red Hat Bugzilla – Bug 1022015
haproxy local-gear should not be reenabled when activating if it's currently disabled
Last modified: 2015-05-14 19:31:12 EDT
Description of problem: When a scalable app has enough gears such that the local-gear has been disabled (e.g. 3 gears), the local-gear is reenabled during a deployment/activation when it should remain disabled. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a scalable app 2. Scale up to 3 gears 3. Verify in the haproxy-status page that the local-gear is disabled 4. Make a change and deploy the change to the app Actual results: local-gear is enabled Expected results: local-gear remains disabled
https://github.com/openshift/origin-server/pull/3967
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/a0014a2b7c36758947968a6ada2e68d59e9aef7a Bug 1022015: Don't enable a disabled local gear on a git push.
Checked on devenv_3934, during git push, the MAINT gear will not be enabled. Move bug to verified.