Bug 1693035

Summary: Fluentd doesn't output it's logs to STDOUT when LOGGING_FILE_PATH=console
Product: OpenShift Container Platform Reporter: Qiaoling Tang <qitang>
Component: LoggingAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: anli, aos-bugs, jcantril, jkarasek, nhosoi, rmeggins
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1690232 Environment:
Last Closed: 2019-06-06 02:00:29 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: 1690232, 1693036, 1693043    
Bug Blocks:    

Description Qiaoling Tang 2019-03-27 01:27:31 UTC
+++ This bug was initially created as a clone of Bug #1690232 +++

Description of problem:

Per https://bugzilla.redhat.com/show_bug.cgi?id=1651884#c4, when  LOGGING_FILE_PATH=console, should use "oc logs $fluentd-pod" to view fluentd pod logs, but in fact, it doesn't show pod logs. 

Set LOGGING_FILE_PATH=console makes fluentd store it's own logs to "/opt/app-root/src/console"


Version-Release number of selected component (if applicable):
ose-logging-fluentd-v3.11.98-2

How reproducible:
Always

Steps to Reproduce:
1.Deploy logging
2.Set LOGGING_FILE_PATH=console in ds/fluentd, then check fluentd pod logs:
$ oc set env ds/fluentd LOGGING_FILE_PATH=console

$ oc exec fluentd-dvmk4 env |grep LOGGING_FILE
LOGGING_FILE_PATH=console
LOGGING_FILE_AGE=10
LOGGING_FILE_SIZE=1024000

$ oc logs fluentd-dvmk4
=============================
Fluentd logs have been redirected to: console
If you want to print out the logs, use command:
oc exec <pod_name> -- logs
=============================
3.

Actual results:


Expected results:
Should be able to use "oc logs $fluentd-pod" to view pod log when LOGGING_FILE_PATH=console


Additional info:

Comment 1 Rich Megginson 2019-03-27 01:33:47 UTC
Can you reproduce this bug in 3.11?

Comment 2 Qiaoling Tang 2019-03-27 01:37:51 UTC
Yes, this bug is for 3.11, and I'm trying to reproduce in 3.10 and 3.9, will open bug if I could reproduce.

Comment 4 Anping Li 2019-04-16 07:43:09 UTC
The log are in console with logging-fluentd:v3.11.104

Comment 6 errata-xmlrpc 2019-06-06 02:00:29 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-2019:0794