Bug 1105660 - ActiveModel::Observing removed from rails > 4.0
Summary: ActiveModel::Observing removed from rails > 4.0
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Jhon Honce
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-06 16:21 UTC by Antonio Parisi
Modified: 2023-09-14 02:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-12 19:42:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


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