From fb28b8fa70c6af4dd90454add5a0d05c7227c05c Mon Sep 17 00:00:00 2001 From: Adam Grare Date: Thu, 7 Sep 2017 09:18:08 -0400 Subject: [PATCH] Fix event_catcher blacklisted events logging The event catcher runner was printing the blacklisted events array using the VMDBLogger#log_hashes method. Now that this method calls .to_hash on the argument (https://github.com/ManageIQ/manageiq-gems-pending/pull/268) this is throwing an exception for non-hash type arguments. Instead of using log_hashes just log the elements of the array joined by newlines directly. --- .../manageiq/providers/base_manager/event_catcher/runner.rb | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/app/models/manageiq/providers/base_manager/event_catcher/runner.rb b/app/models/manageiq/providers/base_manager/event_catcher/runner.rb index 168363f1a1a..36029376114 100644 --- a/app/models/manageiq/providers/base_manager/event_catcher/runner.rb +++ b/app/models/manageiq/providers/base_manager/event_catcher/runner.rb @@ -18,8 +18,7 @@ def after_initialize do_exit("EMS ID [#{@cfg[:ems_id]}] failed authentication check.", 1) unless @ems.authentication_check.first @filtered_events = @ems.blacklisted_event_names - _log.info("#{log_prefix} Event Catcher skipping the following events:") - $log.log_hashes(@filtered_events) + _log.info("#{log_prefix} Event Catcher skipping the following events:\n#{@filtered_events.to_a.join("\n")}") configure_event_flooding_prevention if worker_settings.try(:[], :flooding_monitor_enabled)