Red Hat Bugzilla – Bug 1336859
After provider create, error in logs
Last modified: 2016-07-13 12:48:04 EDT
Description of problem: After provider create, error in logs This bug was confirmed by lsmola, who has more details Version-Release number of selected component (if applicable): 5.6.0.6 How reproducible: 100% Steps to Reproduce: 1. Add a new provider (RHOS tested) 2. 3. Actual results: Error about missing method appears in logs Expected results: No error Additional info: [----] E, [2016-05-17T09:27:35.184855 #7842:1151994] ERROR -- : MIQ(MiqQueue#deliver) Message id: [203047], Error: [undefined method `stop_event_monitor' for #<Class:0x0000000d50dc98>] [----] E, [2016-05-17T09:27:35.186162 #7842:1151994] ERROR -- : [NoMethodError]: undefined method `stop_event_monitor' for #<Class:0x0000000d50dc98> Method:[rescue in deliver] [----] E, [2016-05-17T09:27:35.186319 #7842:1151994] ERROR -- : /opt/rh/cfme-gemset/bundler/gems/rails-4d7aba7edcd6/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing' /var/www/miq/vmdb/app/models/miq_queue.rb:347:in `block in deliver' /opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:89:in `block in timeout' /opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `block in catch' /opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `catch' /opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `catch' /opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:104:in `timeout' /var/www/miq/vmdb/app/models/miq_queue.rb:343:in `deliver' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:106:in `deliver_queue_message' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:134:in `deliver_message' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:152:in `block in do_work' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:146:in `loop' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:146:in `do_work' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:334:in `block in do_work_loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:331:in `loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:331:in `do_work_loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:153:in `run' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:128:in `start' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:21:in `start_worker' /var/www/miq/vmdb/app/models/miq_worker.rb:346:in `block in start' /opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.3/lib/nakayoshi_fork.rb:24:in `fork' /opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.3/lib/nakayoshi_fork.rb:24:in `fork' /var/www/miq/vmdb/app/models/miq_worker.rb:344:in `start' /var/www/miq/vmdb/app/models/miq_worker.rb:274:in `start_worker' /var/www/miq/vmdb/app/models/miq_worker.rb:154:in `block in sync_workers' /var/www/miq/vmdb/app/models/miq_worker.rb:154:in `times' /var/www/miq/vmdb/app/models/miq_worker.rb:154:in `sync_workers' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:52:in `block in sync_workers' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `each' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `sync_workers' /var/www/miq/vmdb/app/models/miq_server.rb:173:in `start' /var/www/miq/vmdb/app/models/miq_server.rb:264:in `start' /var/www/miq/vmdb/lib/workers/evm_server.rb:65:in `start' /var/www/miq/vmdb/lib/workers/evm_server.rb:92:in `start' /var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `<main>'
https://github.com/ManageIQ/manageiq/pull/8785
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/406504073771ee4e91908aa54aae9bd791c20916 commit 406504073771ee4e91908aa54aae9bd791c20916 Author: Ladislav Smola <lsmola@redhat.com> AuthorDate: Wed May 18 17:56:15 2016 +0200 Commit: Ladislav Smola <lsmola@redhat.com> CommitDate: Fri May 20 15:13:10 2016 +0200 Check for EMS new_record before stopping event monitor Check for EMS new_record before stopping event monitor Fixes BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1336859 app/models/manageiq/providers/openstack/manager_mixin.rb | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
No such Error when RHOS provider is added. Verified: 5.6.0.9-rc2.20160531154046_b4e2f6d
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348