This bug could be reproduced with rubygem-openshift-origin-controller-1.17.11-1.el6op.noarch in puddle 2.0.z/2014-01-22.1 +++ This bug was initially created as a clone of Bug #1035186 +++ Description of problem: For a HA enabled scalable app, when trying to scale-up in the secondary haproxy-gear, will get failed due to the broker auth does not exist on the gear. [459590177713071029485568-bmengdev.dev.rhcloud.com 459590177713071029485568]\> haproxy_ctld -u /var/lib/openshift/459590177713071029485568/haproxy//usr/bin/remove-gear:36:in `read': No such file or directory - /var/lib/openshift/459590177713071029485568/.auth/token (Errno::ENOENT) from /var/lib/openshift/459590177713071029485568/haproxy//usr/bin/remove-gear:36:in `execute' from /var/lib/openshift/459590177713071029485568/haproxy//usr/bin/remove-gear:208:in `<main>' Version-Release number of selected component (if applicable): devenv_4077 How reproducible: always Steps to Reproduce: 1.Create scalable app 2.Make the app HA via rest api 3.SSH login to the secondary haproxy gear 4.Try to scale-up with haproxy_ctld cmd Actual results: It will fail due to the broker auth does not exist on the gear. Expected results: Should be able to scale up manually on all the haproxy gears. Additional info: --- Additional comment from Dan McPherson on 2014-01-15 09:36:24 EST --- https://github.com/openshift/origin-server/pull/4477 --- Additional comment from openshift-github-bot on 2014-01-15 19:20:22 EST --- Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/e5f5265c5ddbe6f3f98a1df1d1f01961563858b1 Bug 1035186 --- Additional comment from Hou Jianwei on 2014-01-16 04:38:03 EST --- Verified on devenv_4229 1. Create a scalable app and make it HA enabled 2. SSH to the 2nd gear, scale it up with 'haproxy_ctld -u' Result: The app scaled up successfully.
verified with puddle-2014-01-30 52ec29d03eefa9b7e700002b-demo.ose203.example.com 52ec29d03eefa9b7e700002b]\> haproxy_ctld -u
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. http://rhn.redhat.com/errata/RHBA-2014-0209.html