Bug 1626553
| Summary: | [3.11] 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 CURRENTRELEASE | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.11.0 | CC: | anli, aos-bugs, haowang, jcantril, rmeggins |
| Target Milestone: | --- | Keywords: | OpsBlocker |
| Target Release: | 3.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openshift3/ose-logging-fluentd:v3.11.3-1 | Doc Type: | Bug Fix |
| Doc Text: |
If this bug requires documentation, please select an appropriCause: 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.ate Doc Type value.
|
Story Points: | --- |
| Clone Of: | 1626552 | Environment: | |
| Last Closed: | 2018-12-21 15:23:01 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, 1626552 | ||
| Bug Blocks: | |||
|
Comment 2
Jeff Cantrill
2018-09-10 13:04:18 UTC
The fix is in openshift3/ose-logging-fluentd/images/v3.11.6-1, fluent-plugin-kubernetes_metadata_filter-1.2.0 Closing bugs that were verified and targeted for GA but for some reason were not picked up by errata. This bug fix should be present in current 3.11 release content. |