Bug 1693036 - Fluentd doesn't output it's logs to STDOUT when LOGGING_FILE_PATH=console
Summary: Fluentd doesn't output it's logs to STDOUT when LOGGING_FILE_PATH=console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.9.z
Assignee: Noriko Hosoi
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1690232 1693043
Blocks: 1693035
TreeView+ depends on / blocked
 
Reported: 2019-03-27 01:51 UTC by Qiaoling Tang
Modified: 2019-06-06 06:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1690232
Environment:
Last Closed: 2019-06-06 06:56:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 1579 0 None None None 2019-03-30 04:36:06 UTC
Red Hat Product Errata RHBA-2019:0788 0 None None None 2019-06-06 06:56:07 UTC

Description Qiaoling Tang 2019-03-27 01:51:49 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):
logging-fluentd-v3.9.74-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/logging-fluentd LOGGING_FILE_PATH=console

[root@qe-anli39-master-etcd-nfs-1 ~]# oc exec logging-fluentd-ds6zq env |grep LOGGING_FILE
LOGGING_FILE_PATH=console
LOGGING_FILE_AGE=10
LOGGING_FILE_SIZE=1024000
[root@qe-anli39-master-etcd-nfs-1 ~]# oc logs logging-fluentd-ds6zq
=============================
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:59:09 UTC
I don't understand why the 3.x releases have this problem with LOGGING_FILE_PATH=console - this should have been fixed a long time ago - is this a regression?

Comment 2 Rich Megginson 2019-03-27 01:59:51 UTC
(In reply to Rich Megginson from comment #1)
> I don't understand why the 3.x releases have this problem with
> LOGGING_FILE_PATH=console - this should have been fixed a long time ago - is
> this a regression?

Note that the implementation in 4.x is completely different, and LOGGING_FILE_PATH=console was broken in 4.x for a completely different reason.

Comment 5 Anping Li 2019-04-22 13:36:04 UTC
The fluentd can be found in console using version v3.9.78

Comment 7 errata-xmlrpc 2019-06-06 06:56:05 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:0788


Note You need to log in before you can comment on or make changes to this bug.