Failed to start Foreman after rubygem-json update
I'm running Foreman 1.1stable on CentOS 6.3 x86_64
Foreman died after updating rubygem-json package today.
Package updated from the Foreman repository
- /etc/init.d/foreman restart
Stopping foreman: Foreman was not running. [FAILED]
Starting foreman: /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:87:in `materialize': Could not find json-1.6.6 in any of the sources (Bundler::GemNotFound)
from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:81:in `map!'
from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:81:in `materialize'
from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/definition.rb:90:in `specs'
from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/definition.rb:135:in `specs_for'
from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/definition.rb:124:in `requested_specs'
from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/environment.rb:23:in `requested_specs'
from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/runtime.rb:11:in `setup'
from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler.rb:107:in `setup'
from /usr/share/foreman/script/rails:5:in `require'
- diff Gemfile.lock Gemfile.lock_orig
< json (1.6.8)
after I managed to start foreman.
I would like to make sure that this is a proper fix and won't heart anything else or if other actions required.
That was really strange having kind of simple bug in stable version.
#1 Updated by Dominic Cleal over 6 years ago
- Category set to Packaging
- Status changed from New to Ready For Testing
- Assignee set to Lukas Zapletal
- Target version set to 1.2.0
The issue here is there's no posttrans run after a rubygem's updated. In the short term, a new 1.1 stable release should help as it'll cause bundler to update.
In the longer term, lzap's bundler_ext patch will resolve this.