Description of problem:The current evm.log file is littered with meaningless log lines for what appears to be all messages. Please either remove this log line or set a default minimum size so as to be useful. Alternatively, just re-add the message size into the ".put" as it once was *and* eliminate the warn message. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Sample meaningless log line follows: ===== MIQ(MiqQueue#warn_if_large_payload) /var/www/miq/vmdb/app/models/ems_event.rb:55 called with large payload (args: 962 bytes, data: 0 bytes) Message id: [6643], id: [], Zone: [default], Role: [event], Server: [], Ident: [ems], Target id: [3], Instance id: [], Task id: [], Command: [EmsEvent.add_vc], Timeout: [600], Priority: [100], State: [ready], Deliver On: [], Data: [], Args: [{"key"=>"18753427", "chainId"=>"18753427", "createdTime"=>"2015-09-24T13:09:42.784206Z", "userName"=>"MANAGEIQ\\evm", "fullFormattedMessage"=>"Cannot login MANAGEIQ\\evm.252.16", "changeTag"=>"", "ipAddress"=>"192.168.252.16", "eventType"=>"BadUsernameSessionEvent"}] ====
https://github.com/ManageIQ/manageiq/pull/5393
https://github.com/ManageIQ/manageiq/pull/5716
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/f7ef4a4715134252b65192deae115f6d003df7ec commit f7ef4a4715134252b65192deae115f6d003df7ec Author: Nick Carboni <ncarboni> AuthorDate: Fri Dec 4 14:03:24 2015 -0500 Commit: Nick Carboni <ncarboni> CommitDate: Fri Dec 4 14:07:29 2015 -0500 Remove large payload warnings from miq_queue https://bugzilla.redhat.com/show_bug.cgi?id=1274336 app/models/miq_queue.rb | 11 ----------- spec/models/miq_queue_spec.rb | 14 -------------- 2 files changed, 25 deletions(-)
Removed the check for payload size.
Verified in 5.6.0.1-beta2
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/RHBA-2016:1348