+++ This bug was initially created as a clone of Bug #1796133 +++ Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Jeff Cantrill on 2020-01-29 18:23:47 UTC --- Fluent logs were written to disk in order to: 1. Avoid a feedback loop of collecting its own logs 2. Allow collector investigation when there are issues by being able to review persistent logs. This strategy has proven to be problematic and can lead to node issues if fluent log rotation is now working properly and logs are not being cleaned up. Logs should be reverted to be written to stdout and excluded from collection. The pattern for the container logs for thcollector: sh-4.4# ls | grep fluent fluentd-m65p9_openshift-logging_fluentd-591768f9629810d85fbe623c4afc76bd96424e67e48ccdc2128f40cd0a94611d.log fluentd-m65p9_openshift-logging_fluentd-9872757d29cc899822c2586f9e519c8d365044ab7330371564085ba6e600fbf6.log Possibly partially responsible for https://bugzilla.redhat.com/show_bug.cgi?id=1780698 --- Additional comment from Jeff Cantrill on 2020-01-29 20:30:36 UTC --- This should be backported to 4.2 and 4.3
Awaiting cherrypick approval form patch manager
Verified on clusterlogging.4.3.20-202005141057
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-2020:2184