Bug 830717 - get error message when running rhc-outage from instance
Summary: get error message when running rhc-outage from instance
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-11 10:01 UTC by Meng Bo
Modified: 2015-05-15 01:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-11 14:51:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Meng Bo 2012-06-11 10:01:30 UTC
Description of problem:
run /var/www/stickshift/site/app/subsites/status/rhc-outage from instance, will get error message and cannot call new issue.

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

How reproducible:
always

Steps to Reproduce:
1../var/www/stickshift/site/app/subsites/status/rhc-outage
2.
3.
  
Actual results:
[root@ip-10-12-183-234 site]# ./app/subsites/status/rhc-outage new
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:779:in `report_activate_error': RubyGem version error: arel(2.0.9 not ~> 2.0.10) (Gem::LoadError)
	from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:214: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/custom_require.rb:35:in `require'
	from /var/www/stickshift/site/app/subsites/status/lib/database.rb:2
	from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
	from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
	from ./app/subsites/status/rhc-outage:14


Expected results:
rhc-outage should not return error and can be called successfully.

Additional info:

Comment 1 Clayton Coleman 2012-06-11 14:51:33 UTC
You have to run 'bundle exec ./rhc-outage ...' from that dir now instead of 'rhc-outage ...'


Note You need to log in before you can comment on or make changes to this bug.