Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1510381 - undefined method `purge_timer'
Summary: undefined method `purge_timer'
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: cfme-future
Assignee: Marek Aufart
QA Contact: Omri Hochman
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-07 09:55 UTC by Alexander Braverman
Modified: 2018-10-17 13:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-10-17 13:22:43 UTC
Category: Bug
Cloudforms Team: Openstack
Target Upstream Version:

Attachments (Terms of Use)

Description Alexander Braverman 2017-11-07 09:55:28 UTC
Description of problem:
Error collected from evm.log in appliance dedicated for RHOS 10 sync:

[----] E, [2017-11-07T04:23:29.564884 #63620:124d12c] ERROR -- : [NoMethodError]: undefined method `purge_timer' for #<Class:0x000000131cd4b0>  Method:[rescue in deliver]
[----] E, [2017-11-07T04:23:29.565091 #63620:124d12c] ERROR -- : /opt/rh/cfme-gemset/gems/activerecord-5.0.3/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-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_queue_worker_base/runner.rb:107:in `deliver_queue_message'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:135:in `deliver_message'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:153:in `block in do_work'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:147:in `loop'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:147:in `do_work'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:336:in `block in do_work_loop'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:333:in `loop'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:333:in `do_work_loop'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:155:in `run'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:130: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:339:in `block in start_runner'
/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:337:in `start_runner'
/var/www/miq/vmdb/app/models/miq_worker.rb:348:in `start'
/var/www/miq/vmdb/app/models/miq_worker.rb:266:in `start_worker'
/var/www/miq/vmdb/app/models/miq_worker.rb:150:in `block in sync_workers'
/var/www/miq/vmdb/app/models/miq_worker.rb:150:in `times'
/var/www/miq/vmdb/app/models/miq_worker.rb:150:in `sync_workers'
/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:53: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:160:in `start'
/var/www/miq/vmdb/app/models/miq_server.rb:251:in `start'
/var/www/miq/vmdb/lib/workers/evm_server.rb:65:in `start'
/var/www/miq/vmdb/lib/workers/evm_server.rb:91:in `start'
/var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `<main>'

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure OSP provider (RHOS 10) with zone dedicated for sync and AMQP is the event listener
2. Add appliance to OSP sync zone with the appropriate roles:
 - Capacity & Utilization Coordinator 
 - Capacity & Utilization Data Collector
 - Capacity & Utilization Data Processor
 - Event Monitor 
 - Provider Inventory
 - Provider Operations 
3. Let it sync while creating and destroying instances on RHOS

Actual results:
Error in the evm.log - [NoMethodError]: undefined method `purge_timer' for #<Class:0x000000131cd4b0>

Expected results:
No errors

Additional info:

Comment 2 Dave Johnson 2017-11-07 10:03:07 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.

Comment 4 Sam Lucidi 2018-10-17 13:22:43 UTC
Appears to have been fixed since 5.9. If this recurs, please open a new bz.

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