Bug 1439308
Summary: | Excessive log lines for "Initializing DRb Connection to MiqServer with ID" | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | Appliance | Assignee: | Joe Rafaniello <jrafanie> |
Status: | CLOSED ERRATA | QA Contact: | luke couzens <lcouzens> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.7.0 | CC: | abellott, jhardy, jrafanie, obarenbo, simaishi |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.7.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | appliance:upgrade | ||
Fixed In Version: | 5.7.2.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1438935 | Environment: | |
Last Closed: | 2017-04-12 14:47:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1438935 | ||
Bug Blocks: |
Comment 2
Joe Rafaniello
2017-04-05 19:09:50 UTC
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/0a1ad0e0a0d12c6662e420322cc92d2d4be83c82 commit 0a1ad0e0a0d12c6662e420322cc92d2d4be83c82 Author: Gregg Tanzillo <gtanzill> AuthorDate: Tue Apr 4 18:24:33 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Thu Apr 6 12:35:12 2017 -0400 Merge pull request #14638 from jrafanie/fix_worker_monitor_drb_new_client_each_time Make worker_monitor_drb act like a reader again! (cherry picked from commit 56ee45a63c780fff16722f91ba09d6acc0642ca0) https://bugzilla.redhat.com/show_bug.cgi?id=1439308 app/models/miq_worker/runner.rb | 29 +++++++++++++++-------------- spec/models/miq_worker/runner_spec.rb | 8 ++++++++ 2 files changed, 23 insertions(+), 14 deletions(-) Hi Joe, whats the best way to reproduce this one? Thanks, Luke Verified in 5.7.2.1 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/RHSA-2017:0898 |