Bug 1626552
| Summary: | [3.10] fluentd pods are running with error logs which makes fill up disk very quickly. | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Rich Megginson <rmeggins> | |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.10.0 | CC: | anli, aos-bugs, haowang, rmeggins | |
| Target Milestone: | --- | Keywords: | OpsBlocker | |
| Target Release: | 3.10.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openshift3/logging-fluentd:v3.10.45-1 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Fluentd generates events internally for some unknown reason with the OneEventStream class. This class does not have the `empty?` method. The kubernetes metadata filter was using the `empty?` method on the EventStream object to avoid processing an empty stream.
Consequence: Fluentd issues many error messages complaining about a missing `empty?` method. This overwhelms the container logging and causes disk issues.
Fix: The kubernetes metadata filter was changed to only call the `empty?` method on objects which have that method.
Result: fluentd logs should not be filled with this message.
|
Story Points: | --- | |
| Clone Of: | 1626281 | |||
| : | 1626553 (view as bug list) | Environment: | ||
| Last Closed: | 2018-11-11 16:39:11 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: | 1626281 | |||
| Bug Blocks: | 1626553 | |||
|
Comment 3
Anping Li
2018-10-10 03:39:43 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/RHSA-2018:2709 |