Bug 1105660

Summary:	ActiveModel::Observing removed from rails > 4.0
Product:	OKD	Reporter:	Antonio Parisi <ant.parisi>
Component:	Containers	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED WORKSFORME	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.x	CC:	admiller, ant.parisi, dmcphers, lmeyer, misalunk, mmccomas
Target Milestone:	---	Keywords:	UpcomingRelease
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-12 19:42:21 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 Antonio Parisi 2014-06-06 16:21:54 UTC

Description of problem:
Hello,
from rails >4.0 ActiveModel Observers have been removed and moved out as a gem https://github.com/rails/rails/commit/ccecab3ba950a288b61a516bf9b6962e384aae0b, the alias `ctl_app` (gear) is still using it, and the `openshift-origin-common.gemspec` is not using `rails-observers` gem.
so, actually, I was trying to use rails 4.1.1 with `scl enable ruby193`, and the error basically is this:
/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-common-1.24.3/lib/openshift-origin-common/models/model.rb:13:in `<class:Model>': uninitialized constant ActiveModel::Observing (NameError)

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


How reproducible:


Steps to Reproduce:
1. use ruby 1.9.3
2. upgrade your app to rails > 4.0 (e.g. 4.1.1)
3. run `bundle install`
4. then, `ctl_app` (gear) will go in error.

Actual results:
/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-common-1.24.3/lib/openshift-origin-common/models/model.rb:13:in `<class:Model>': uninitialized constant ActiveModel::Observing (NameError)

Expected results:


Additional info:

Comment 1 Luke Meyer 2014-08-20 19:29:24 UTC

The ActiveModel used by ctl_app/gear *should* not depend in any way on what has been installed in the app. The ruby cartridge build step runs bundle install in such a way that the gems end up in app-root/runtime/repo/vendor/bundle which should only be used by the app.

Is it possible that when you ran bundle install (manually?), gems were installed in $GEM_HOME (~/.gem) instead? Those would be used by the gear/cartridge. Could you give more detail on exactly how / where you ran "bundle install" (and with what arguments if any)?

Comment 2 Red Hat Bugzilla 2023-09-14 02:09:31 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days