Description of problem: dbomatic will fail to (re)start, with the following log entry: 2012-01-03 16:43:20 ERROR /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.10/lib/active_support/dependencies.rb:304:in `depend_on': No such file to load -- lib/image 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.10/lib/active_support/dependencies.rb:216:in `require_dependency' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/engine.rb:138:in `eager_load!' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/engine.rb:137:in `each' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/engine.rb:137:in `eager_load!' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/engine.rb:135:in `each' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/engine.rb:135:in `eager_load!' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/application.rb:108:in `eager_load!' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/application/finisher.rb:41 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/initializable.rb:25:in `instance_exec' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/initializable.rb:25:in `run' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/initializable.rb:50:in `run_initializers' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/initializable.rb:49:in `each' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/initializable.rb:49:in `run_initializers' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/application.rb:134:in `initialize!' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/application.rb:77:in `send' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/application.rb:77:in `method_missing' 2012-01-03 16:43:20 ERROR from /usr/share/aeolus-conductor/config/environment.rb:23 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require' 2012-01-03 16:43:20 ERROR from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require' 2012-01-03 16:43:20 ERROR from /usr/share/aeolus-conductor/dbomatic/dbomatic:274 Version-Release number of selected component (if applicable): 0.8.0 in testing repo How reproducible: 100% Steps to Reproduce: 1. With latest from testing repo, "service conductor-dbomatic restart" 2. Wait a couple seconds and run "service conductor-dbomatic status" -- will show "active (exited)" 3. View /var/log/aeolus-conductor/dbomatic.log Though this appears to be a dbomatic bug, it's actually choking on code in Conductor.
This is caused by a change I made that, curiously, did not impact Conductor itself. I'll fix this up.
Patch: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-January/007819.html
I'm seeing this while testing with ... aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch Hey Matt, the patch referenced in comment#2 appears to have been NACK'd, any updates? Any information I can provide to assist debugging? Note, this appears to be the same issue reported in bug#768832.
(In reply to comment #3) > Hey Matt, the patch referenced in comment#2 appears to have been NACK'd, any > updates? Any information I can provide to assist debugging? Oops, I think I misinterpreted feedback from Jan in that thread. The patch appears to resolve the reported conductor-dbomatic service start issue for me.
Pushed to master: commit d2a37e2bf0d53ecbd836a693ade68da601419d4b Author: Matt Wagner <matt.wagner> Date: Tue Jan 3 17:41:46 2012 -0500 Reference lib/image by full path Resolves https://bugzilla.redhat.com/show_bug.cgi?id=771505
*** Bug 768832 has been marked as a duplicate of this bug. ***
dbomatic started successfully. [root@dell-pe1950-02 ~]# service conductor-dbomatic restart [ OK ] down conductor-dbomatic: [ OK ] [ OK ] conductor-dbomatic: [ OK ] [root@dell-pe1950-02 ~]# service conductor-dbomatic status dbomatic (pid 12449) is running... [root@dell-pe1950-02 ~]# ps -auxf |grep dbomatic Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.8/FAQ root 12473 0.0 0.0 103236 836 pts/2 S+ 00:57 0:00 \_ grep dbomatic aeolus 12449 5.9 9.9 237844 100920 ? S 00:54 0:11 /usr/bin/ruby /usr/share/aeolus-conductor/dbomatic/dbomatic dbomatic.log: 012-01-08 01:44:42 INFO DBOmatic starting up 2012-01-08 01:44:54 INFO Beginning main event loop 2012-01-08 01:44:54 DEBUG Deltacloud instances refresh started 2012-01-08 01:44:54 DEBUG Deltacloud instances refresh completed 2012-01-08 01:45:54 DEBUG Deltacloud instances refresh started 2012-01-08 01:45:54 DEBUG Deltacloud instances refresh completed 2012-01-08 01:46:54 DEBUG Deltacloud instances refresh started 2012-01-08 01:46:54 DEBUG Deltacloud instances refresh completed verified on: [root@dell-pe1950-02 rheltempwes]# rpm -qa | grep aeolus aeolus-configure-2.6.0-0.20120105171403gitf0043e8.el6.noarch aeolus-conductor-doc-0.9.0-0.20120105223209git5e068fe.el6.noarch rubygem-arel-2.0.10-0.aeolus.el6.noarch rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch rubygem-aeolus-image-0.4.0-0.20120105171419git8108b42.el6.noarch aeolus-conductor-0.9.0-0.20120105223209git5e068fe.el6.noarch aeolus-all-0.9.0-0.20120105223209git5e068fe.el6.noarch rubygem-aeolus-cli-0.4.0-0.20120105171410git2c6b457.el6.noarch aeolus-conductor-daemons-0.9.0-0.20120105223209git5e068fe.el6.noarch