Bug 808729

Summary: failed to auto GEAR_UP when set the auto scaling enabled
Product: OKD Reporter: Meng Bo <bmeng>
Component: ocAssignee: Jhon Honce <jhonce>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.xCC: mmcgrath, rmillner, xtian
Target Milestone: ---Keywords: Regression, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-13 18:33:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Meng Bo 2012-03-31 11:09:02 UTC 
Description of problem:
enable the scalable app auto scaling, trigger the auto scale up function, will get error message, and scale-up cannot be successful.

Version-Release number of selected component (if applicable):
stage-2.0.8

How reproducible:
always

Steps to Reproduce:
1.create scalable app
2.ssh login to the app and start the auto scaling
haproxy_ctld --debug &
3.do some parallel connections and trigger the auto scale up
4.check the scale_events.log
tailf <gear_name>/logs/scale_events.log
  
Actual results:
Auto scale up got failed 

Expected results:
auto scale up should not get any problem and the gears count should be increased.

Additional info:
I, [2012-03-31T06:47:57.872265 #26325]  INFO -- : GEAR_UP - capacity: 390.0% gear_count: 1 sessions: 39 up_thresh: 90.0%
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- rest-client (LoadError)
	from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
	from /usr/libexec/stickshift/cartridges/embedded/haproxy-1.4/info/bin/add-gear:4


Cannot reproduce this issue on devenv-stage_155
Comment 1 Mike McGrath 2012-04-02 15:46:03 UTC 
Assigning to the Jhon-a-nator
Comment 2 Jhon Honce 2012-04-02 17:12:54 UTC 
commit d4aaf08f6e28364d3f0a82a2a0b0eb2f23baff90

Added dependency to spec file.
Comment 3 Rob Millner 2012-04-04 18:17:06 UTC 
John, can this bug be moved to ON_QA?   Thanks!
Comment 4 Jhon Honce 2012-04-04 18:29:49 UTC 
Yes, I had punted to Mike to ensure commit got merged where ever else it was needed.
Comment 5 Xiaoli Tian 2012-04-05 13:36:10 UTC 
Verified it on devenv_1696, it's fixed.