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

Bug 1866531

Summary: LOG-802 forwarder: infrastructure logs are sent to application pipelines.
Product: OpenShift Container Platform Reporter: Alan Conway <aconway>
Component: LoggingAssignee: Alan Conway <aconway>
Status: CLOSED ERRATA QA Contact: Qiaoling Tang <qitang>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.6CC: aos-bugs, jcantril, mburke, qitang
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-core
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 15:09:34 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:

Description Alan Conway 2020-08-05 19:55:35 UTC
Description of problem:

If there is no pipeline with an infrastructure input, infrastructure logs are forwarded on pipelines with application input. In the following example, infrastructure logs are sent to output ff.


spec:
 outputs:
 - name: ff
 type: fluentdForward
 url: tcp://192.168.0.103:24224
 fluentForward: {}
pipelines:
 - name: myPipeline
 inputRefs: [ application ]
 outputRefs: [ ff ]

Version-Release number of selected component (if applicable):

4.6 and 4.5.z

How reproducible:

100%

Steps to Reproduce:
1. Set up a fluentd instance outside the cluster
2. Create the clf instance in the cluster using the YAML above modified with the address of your fluentd.


Actual results:

Flood of infrastructure logs forwarded to the fluentd

Expected results:

Only application logs forwarded

Comment 1 Qiaoling Tang 2020-08-06 01:57:51 UTC
If forward infrastructure logs only, then no logs will be found in the receiver.

Comment 2 Alan Conway 2020-08-20 12:31:54 UTC
Fix in progress https://github.com/openshift/cluster-logging-operator/pull/649
Has unresolved test failures.

Comment 3 Jeff Cantrill 2020-08-21 14:11:17 UTC
Moving to UpcomingSprint for future evaluation

Comment 6 Qiaoling Tang 2020-08-26 03:21:33 UTC
Tested with clusterlogging.4.6.0-202008252031.p0:

1. if only forward infrastructure logs, only journal logs are forwarded, the container logs in openshift*, kube*, default namespaces are not forwarded.

2. if only forward application logs, only app logs could be forwarded.

3. if forward application and infrastructure logs, then the container logs in openshift*, kube*, default namespaces could be forwarded.


The container logs in openshift*, kube*, default namespaces are infrastructure logs, they should be forwarded when only forward infrastructure logs.

Comment 7 Jeff Cantrill 2020-09-12 01:58:19 UTC
Moving to UpcomingSprint as unlikely to be addressed by EOD

Comment 9 Qiaoling Tang 2020-09-18 02:22:18 UTC
Verified with clusterlogging.4.6.0-202009171735.p0

Comment 11 errata-xmlrpc 2020-10-27 15:09:34 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 (OpenShift Container Platform 4.6.1 extras update), 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:4198