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:
You have to run 'bundle exec ./rhc-outage ...' from that dir now instead of 'rhc-outage ...'