Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1588772 - After upgrade to 3.6 some logs are not showing in the Kibana webUI
After upgrade to 3.6 some logs are not showing in the Kibana webUI
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.6.0
All Linux
urgent Severity urgent
: ---
: 3.6.z
Assigned To: Rich Megginson
Anping Li
:
Depends On:
Blocks: 1588827 1588828 1588829
  Show dependency treegraph
 
Reported: 2018-06-07 16:12 EDT by Josh Foots
Modified: 2018-06-28 03:55 EDT (History)
4 users (show)

See Also:
Fixed In Version: logging-fluentd-container-v3.6.173.0.124-1
Doc Type: Bug Fix
Doc Text:
Cause: The incoming data has a field `record["event"]` that is a String value and not the Hash value expected by the transform_eventrouter code. Consequence: This causes the code to throw an error and fluentd to emit an error like this: ``` error_class=NoMethodError error="undefined method `key?' for \"request\":String" ``` Fix: The transform_eventrouter code has been changed to only process the `record["event"]` field if it is a Hash. Result: Records can flow through to Elasticsearch again.
Story Points: ---
Clone Of:
: 1588827 (view as bug list)
Environment:
Last Closed: 2018-06-28 03:54:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github ViaQ/fluent-plugin-viaq_data_model/pull/13 None None None 2018-06-07 18:46 EDT
Red Hat Product Errata RHBA-2018:2007 None None None 2018-06-28 03:55 EDT

  None (edit)
Comment 6 Anping Li 2018-06-14 02:35:05 EDT
The fix works well in logging-fluentd/images/v3.6.173.0.124-2
Comment 8 errata-xmlrpc 2018-06-28 03:54:52 EDT
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-2018:2007

Note You need to log in before you can comment on or make changes to this bug.