Red Hat Bugzilla – Bug 1401935
Heartbeat failure for workers is not reported as ERROR log line but INFO log line
Last modified: 2017-02-27 14:26:27 EST
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/3fb4e9f2b30cd8a5ee04b880fd2a2b1b47d5cbe2 commit 3fb4e9f2b30cd8a5ee04b880fd2a2b1b47d5cbe2 Author: Joe Rafaniello <jrafanie@users.noreply.github.com> AuthorDate: Mon Dec 5 13:29:43 2016 -0500 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Mon Jan 9 12:29:29 2017 -0500 Merge pull request #12889 from carbonin/fix_log_level_for_broker_exit Use the exit code when stopping the vim broker (cherry picked from commit 417e1768d8ada2cbfbc6f1e7eb28c41a6787878a) https://bugzilla.redhat.com/show_bug.cgi?id=1401935 app/models/miq_vim_broker_worker/runner.rb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
I was unable to reproduce the exact error line reported above, but I have found the following: [----] I, [2017-01-27T13:59:11.652053 #3907:4af13c] INFO -- : MIQ(MiqVimBrokerWorker::Runner#on_miq_vim_removed_event) MIQ(MiqVimBrokerWorker::Runner) Attempting to reconnect broker for EMS with address: [xx.xx.xx.xx] due to error: execution expired Should this not also be showing as an error?
That is unrelated to the fix made here. It looks like that line was specifically made info so that's probably the way it is on purpose. This only applies to the messages containing "Stopping Broker." and "Draining Event Queue." Previously these messages were always INFO, after the fix they are dependent on the exit status of the vim broker worker.
Verified in 5.7.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://rhn.redhat.com/errata/RHSA-2017-0320.html