Bug 835775

Summary:	[Origin] ss-register-user fails when latest activesupport gem is installed
Product:	OKD	Reporter:	Johnny Liu <jialiu>
Component:	Pod	Assignee:	Krishna Raman <kraman>
Status:	CLOSED WONTFIX	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.x	CC:	bleanhar, mfisher, rmillner
Target Milestone:	---	Keywords:	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-07-09 02:43:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Johnny Liu 2012-06-27 05:41:25 UTC

Description of problem:


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


How reproducible:
Always

Steps to Reproduce:
1. Gem install rails that will install latest dependency gem packages.
# gem install rails
# gem dependency rails
Gem rails-3.2.6
  actionmailer (= 3.2.6, runtime)
  actionpack (= 3.2.6, runtime)
  activerecord (= 3.2.6, runtime)
  activeresource (= 3.2.6, runtime)
  activesupport (= 3.2.6, runtime)
  bundler (~> 1.0, runtime)
  railties (= 3.2.6, runtime)
# gem list activesupport

*** LOCAL GEMS ***

activesupport (3.2.6)
2. Setup multi node env using rhel6.2 vms, dependency activesupport gem will be installed with specific version
# gem list activesupport

*** LOCAL GEMS ***

activesupport (3.2.6, 3.0.13)

3. Run ss-register-user on broker node

  
Actual results:
# ss-register-user -h
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:233:in `activate': can't activate activesupport (= 3.2.6, runtime) for ["activemodel-3.2.6", "stickshift-common-0.11.2", "stickshift-controller-0.12.3", "swingshift-mongo-plugin-0.8.5"], already activated activesupport-3.0.13 for ["stickshift-controller-0.12.3", "swingshift-mongo-plugin-0.8.5"] (Gem::LoadError)
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:249:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `each'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:249:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `each'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:249:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `each'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:249:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `each'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activate'
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:1082:in `gem'
	from /usr/bin/ss-register-user:18


Expected results:
ss-register-user should be run successfully.

Additional info:

Comment 1 Krishna Raman 2012-07-08 17:14:16 UTC

This is expected. All our code is written to run against 3.0.10 and 3.0.13. If you have 3.2.6 installed , ruby will try to use it and cause this error.

Comment 2 Johnny Liu 2012-07-09 02:43:49 UTC

According to comment 1, close this bug.