Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1798073

Summary:	Write fluent logs to stdout and exclude them from collection
Product:	OpenShift Container Platform	Reporter:	Jeff Cantrill <jcantril>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	anli, aos-bugs
Target Milestone:	---
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1796133	Environment:
Last Closed:	2020-05-27 17:00:45 UTC	Type:	---
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:	1796133
Bug Blocks:

Description Jeff Cantrill 2020-02-04 14:18:45 UTC

+++ 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

Comment 1 Jeff Cantrill 2020-05-11 23:45:00 UTC

Awaiting cherrypick approval form patch manager

Comment 5 Anping Li 2020-05-15 06:03:53 UTC

Verified on clusterlogging.4.3.20-202005141057

Comment 7 errata-xmlrpc 2020-05-27 17:00:45 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/RHBA-2020:2184