Bug 1638899
| Summary: | [3.10] Record is missing kubernetes field when use '--log-driver journald' in /etc/sysconfig/docker | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Rich Megginson <rmeggins> | |
| Component: | Logging | Assignee: | Rich Megginson <rmeggins> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 3.10.0 | CC: | anli, aos-bugs, jcantril, qitang, rmeggins | |
| Target Milestone: | --- | |||
| Target Release: | 3.10.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 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.
|
Story Points: | --- | |
| Clone Of: | 1632648 | |||
| : | 1638900 (view as bug list) | Environment: | ||
| Last Closed: | 2018-11-11 16:39:26 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1632648 | |||
| Bug Blocks: | 1638900, 1638902 | |||
|
Comment 1
Rich Megginson
2018-10-12 18:09:37 UTC
Verified on logging-fluentd-v3.10.56-1 "--log-driver=journald" and "--log-driver journald" all work well. 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/RHSA-2018:2709 |