Bug 1928949

Summary: Using legacy Log Forwarding is not sending logs to the internal Elasticsearch
Product: OpenShift Container Platform Reporter: Jeff Cantrill <jcantril>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: medium    
Version: 4.6CC: anli, aos-bugs, dkulkarn, fan-wxa, jcantril, jniu, mfuruta, mhatanak, naygupta, ocasalsa, rdlugyhe, rh-container
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-core
Fixed In Version: Doc Type: Bug Fix
Doc Text:
* Previously, logs were not sent to managed storage when legacy log forwarding was enabled. This happened because the internal generation of the logforwarding configuration improperly made an either/or decision for logforwarding versus legacy logforwarding. The current release fixes this issue: Logs are sent to managed storage when the logstore is defined in the clusterlogging instance. Additionally, logs are sent to legacy logforwarding when enabled regardless if a managed logstore is enabled or not.
Story Points: ---
Clone Of: 1921263 Environment:
Last Closed: 2021-03-16 23:12:49 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: 1921263    
Bug Blocks: 1905615, 1911477    

Comment 3 Anping Li 2021-03-09 07:43:03 UTC
Verified on 
clusterserviceversion.operators.coreos.com/clusterlogging.4.6.0-202103060451.p0
clusterserviceversion.operators.coreos.com/elasticsearch-operator.4.6.0-202103060018.p0

Comment 5 errata-xmlrpc 2021-03-16 23:12:49 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.21 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-2021:0752