Description of problem: Whenever a queue message is fetched from the server process, we now log a "Initializing DRb Connection" message. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Upgrade to an appliance with fine-1-beta1 2. Start server 3. Each time a worker fetches a queue message, a new DRb client is created and log line below is seen: "Initializing DRb Connection to MiqServer with ID" Additional info: Was introduced in: https://github.com/ManageIQ/manageiq/pull/14365 In commit: https://github.com/ManageIQ/manageiq/commit/e21d1b9ca747cdbdf9c90484e47f7a25ed161d6b for BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1429747
Note, https://github.com/ManageIQ/manageiq/pull/14365 was backported to euwe, so we should clone to 5.7.
https://github.com/ManageIQ/manageiq/pull/14638
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/a9726db194068853599ee173334e5920b7cfe5bd commit a9726db194068853599ee173334e5920b7cfe5bd Author: Joe Rafaniello <jrafanie> AuthorDate: Tue Apr 4 14:59:57 2017 -0400 Commit: Joe Rafaniello <jrafanie> CommitDate: Tue Apr 4 16:08:04 2017 -0400 Make worker_monitor_drb act like a reader again! https://bugzilla.redhat.com/show_bug.cgi?id=1438935 For testing in e21d1b9ca, @worker_monitor_drb was changed to use the method. Unfortunately, this method isn't a reader, so it would create a new drb client each time it was called. It doesn't make sense for this method to make a new drb client each time, so we can cache this client on first access so it functions like a attr_reader now. We can then remove some memoization/caching that occurs in heartbeat since the getter method handles that for us. app/models/miq_worker/runner.rb | 29 +++++++++++++++-------------- spec/models/miq_worker/runner_spec.rb | 8 ++++++++ 2 files changed, 23 insertions(+), 14 deletions(-)
Making this a blocker since it floods the logs. Additionally, it creates a new DRb client each time we process a queue message.
Ugh, wrong bug, removing blocker
*** Bug 1439262 has been marked as a duplicate of this bug. ***
Verified in 5.9.0.3