Description of problem: Given a scalable app has scaled to 2 gears, when it scales up to the 3rd gear, the "stdout: /var/lib/openshift/51ee31813b2c860a4100000f/haproxy//usr/bin/remove-gear:34:in `read': Permission denied" will be found from the scale_events.log in the 2nd gear. Version-Release number of selected component (if applicable): On devenv_3540 How reproducible: Always Steps to Reproduce: 1. Create scalable php application, scale it up to 2 gears 2. Scale up again to the 3rd gear, in the meantime, tailf scale_events.log from both gears in rhcsh Actual results: The following error can be found from the scale_events.log from the 2nd gear <---------------------------------------> D, [2013-07-23T03:36:59.181589 #11172] DEBUG -- : GEAR_DOWN - remove-gear: exit: pid 13296 exit 1 stdout: /var/lib/openshift/51ee31813b2c860a4100000f/haproxy//usr/bin/remove-gear:34:in `read': Permission denied - /var/lib/openshift/8f96d02cf36911e2aeb722000a975b3b/.auth/token (Errno::EACCES) from /var/lib/openshift/51ee31813b2c860a4100000f/haproxy//usr/bin/remove-gear:34:in `initialize' from /var/lib/openshift/51ee31813b2c860a4100000f/haproxy//usr/bin/remove-gear:207:in `new' from /var/lib/openshift/51ee31813b2c860a4100000f/haproxy//usr/bin/remove-gear:207:in `<main>' <---------------------------------------> In above log, "8f96d02cf36911e2aeb722000a975b3b" is the head gear, "51ee31813b2c860a4100000f" is the 2nd gear created on scale up event. Expected results: Should not see above errors Additional info: Giving a low severity since it does not affect any funtionality
Is this a case of HAProxy trying to scale down in the absence of traffic while the user is trying to scale up manually?
(In reply to Abhishek Gupta from comment #1) > Is this a case of HAProxy trying to scale down in the absence of traffic > while the user is trying to scale up manually? Yeah, should be this case.
Fix in pull request https://github.com/openshift/origin-server/pull/3205
The errors are not seen again after above PR is merged. Mark as verified.