Hide Forgot
Description of problem: ------------------------ After a server role is selected/deselected, the corresponding worker thread refuses to start/stop. Note that this issue didn't happen in 5.7.0.1. Version-Release number of selected component (if applicable): ---------------------------- 5.7.0.3 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1.Select a server role and save the configuration setting.Observe that the worker role refuses to start. 2.Alternatively, deselect a server role and observe that the corresponding worker refuses to stop. Actual results: --------------- After a server role is selected/deselected, the corresponding worker thread refuses to start/stop. Expected results: ----------------- After a server role is selected/deselected, the corresponding worker thread should start/stop. Additional info: -----------------
Hi Nandini, Is there an error in the evm.log? Please provide any errors with a backtrace. Perhaps it's the undefined method reload_settings ? If so, maybe it's fixed by this PR: https://github.com/ManageIQ/manageiq/pull/11456
Hi Joe, Yes, it is the undefined method reload_settings error. Here's a snippet from evm.log: [----] E, [2016-10-03T12:34:18.632316 #10200:f6d150] ERROR -- : MIQ(MiqQueue#deliver) Message id: [914], Error: [undefined method `reload_settings' for #<MiqServer:0x0000000b4aa690>] [----] E, [2016-10-03T12:34:18.633408 #10200:f6d150] ERROR -- : [NoMethodError]: undefined method `reload_settings' for #<MiqServer:0x0000000b4aa690> Method:[rescue in deliver] [----] E, [2016-10-03T12:34:18.633692 #10200:f6d150] ERROR -- : /opt/rh/cfme-gemset/gems/activemodel-5.0.0.1/lib/active_model/attribute_methods.rb:433:in `method_missing' /var/www/miq/vmdb/app/models/miq_queue.rb:347:in `block in deliver' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:91:in `block in timeout' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `block in catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:106:in `timeout' /var/www/miq/vmdb/app/models/miq_queue.rb:343:in `deliver' /var/www/miq/vmdb/app/models/miq_server/queue_management.rb:19:in `block in process_miq_queue' /var/www/miq/vmdb/app/models/miq_server/queue_management.rb:15:in `loop' /var/www/miq/vmdb/app/models/miq_server/queue_management.rb:15:in `process_miq_queue' /var/www/miq/vmdb/app/models/miq_server.rb:342:in `block in monitor' /var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store' /var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:30:in `realtime_block' /var/www/miq/vmdb/app/models/miq_server.rb:342:in `monitor' /var/www/miq/vmdb/app/models/miq_server.rb:372:in `block (2 levels) in monitor_loop' /var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store' /var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:30:in `realtime_block' /var/www/miq/vmdb/app/models/miq_server.rb:372:in `block in monitor_loop' /var/www/miq/vmdb/app/models/miq_server.rb:371:in `loop' /var/www/miq/vmdb/app/models/miq_server.rb:371:in `monitor_loop' /var/www/miq/vmdb/app/models/miq_server.rb:254: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>'
Fixed in https://github.com/ManageIQ/manageiq/pull/11456 in backport to euwe branch: https://github.com/ManageIQ/manageiq/commit/2e1da5568c9e10b98914bfbe2e76f1f827cb2651 This will land in the next 5.7.0.4 build.
Verified in 5.8.0.2