Bug 1638902 - [3.7] Record is missing kubernetes field when use '--log-driver journald' in /etc/sysconfig/docker
Summary: [3.7] Record is missing kubernetes field when use '--log-driver journald' in...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.7.z
Assignee: Rich Megginson
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1632648 1638899 1638900
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-12 18:13 UTC by Rich Megginson
Modified: 2019-04-09 23:37 UTC (History)
4 users (show)

Fixed In Version: openshift3/logging-fluentd:v3.7.69-1
Doc Type: Bug Fix
Doc Text:
Cause: When using docker with log-driver journald, the setting in /etc/sysconfig/docker has changed to use --log-driver journald instead of --log-driver=journald Consequence: Fluentd cannot detect that journald is being used, so assumes json-file, and cannot read any kubernetes metadata because it doesn't look for the journald CONTAINER_NAME field. The result is lots of fluentd errors. Fix: Change the way Fluentd detects the docker log driver so that it looks for --log-driver journald in addition to --log-driver=journald. Result: Fluentd can detect the docker log driver, and can correctly process Kubernetes container logs.
Clone Of: 1638900
Environment:
Last Closed: 2019-04-09 23:36:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 1405 0 None None None 2018-10-12 18:13:55 UTC
Red Hat Product Errata RHBA-2019:0617 0 None None None 2019-04-09 23:37:01 UTC

Comment 1 Rich Megginson 2018-10-12 18:15:15 UTC 
https://github.com/openshift/origin-aggregated-logging/pull/1405
Comment 2 Rich Megginson 2018-10-16 21:23:12 UTC 
merged - https://github.com/openshift/origin-aggregated-logging/commit/c8f8f64fc06949c1905378b9ce50b23e3cb5ab91
Comment 5 errata-xmlrpc 2019-04-09 23:36:59 UTC 
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-2019:0617
Note You need to log in before you can comment on or make changes to this bug.