Bug 1632364
Summary: | [3.11] Fluentd cannot handle S2I Logs | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Rich Megginson <rmeggins> |
Component: | Logging | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.11.0 | CC: | anli, aos-bugs, nalentor, qitang, rmeggins, stwalter |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift3/ose-logging-fluentd:v3.11.23-1 | Doc Type: | Bug Fix |
Doc Text: |
Cause: When using docker with the journald log driver, all container logs, including system and plain docker container logs, are logged to the journal, and read by fluentd.
Consequence: fluentd does not know how to handle these non-kubernetes container logs and throws exceptions.
Fix: Treat non-kubernetes container logs as logs from other system services e.g. send them to the .operations.* index.
Result: Logs from non-kubernetes containers are indexed correctly and do not cause any errors.
|
Story Points: | --- |
Clone Of: | 1632361 | Environment: | |
Last Closed: | 2018-11-20 03:10:43 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: | 1632130, 1632361 | ||
Bug Blocks: |
Description
Rich Megginson
2018-09-24 16:06:58 UTC
Tested in ose-logging-fluentd-v3.11.38-1, container 's2i_docker_registry_default_svc_5000_openshift_jboss_eap64_openshift_sha256_25761cad9a7704dbfb3cf353d79d8dfdc54aeded6a01ee3f7064edfb143b4798_ae707a1d' logs could be found in .operations.* index, container 'k8s_sti-build_eap-app-1-build_test1_048f1323-e0a0-11e8-b1c9-42010af00016_0' logs could be found in project.test1.* index. Move this bug to verified. 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:3537 |