Bug 1894640

Summary: Fluent stops sending logs even though logging stack seems functional
Product: OpenShift Container Platform Reporter: Jeff Cantrill <jcantril>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED NEXTRELEASE QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: anli, aos-bugs, jburrell, periklis
Target Milestone: ---Keywords: Reopened, ServiceDeliveryImpact
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-core
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1894639 Environment:
Last Closed: 2021-02-03 16:14:06 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: 1894639    
Bug Blocks:    

Description Jeff Cantrill 2020-11-04 16:58:18 UTC 
+++ This bug was initially created as a clone of Bug #1894639 +++

+++ This bug was initially created as a clone of Bug #1894634 +++

Description of problem:
Fluent seems functional but is not shipping logs and it has a log entry of:

failed to write data into buffer by buffer overflow action=:block

Once the pods are restarted logs start flowing again

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

failed to write data into buffer by buffer overflow action=:block

--- Additional comment from Jeff Cantrill on 2020-11-04 16:55:22 UTC ---

This is modifiable via changes to CL api https://issues.redhat.com/browse/LOG-742

--- Additional comment from Jeff Cantrill on 2020-11-04 16:57:29 UTC ---

This is modifiable via changes to CL api https://issues.redhat.com/browse/LOG-742
Comment 1 Jeff Cantrill 2021-01-28 18:13:42 UTC 
closing next release as this was determined jit would not be pulled into 4.5
Comment 2 Jeff Cantrill 2021-02-03 16:14:06 UTC 
Fixed in the next release.  This can be worked around by either:

* deleting the fluent pods (oc -n openshift-logging delete pods -l component=fluentd)
* Setting clusterlogging instance to "Unmanaged" and manually editing the fluent.conf in the fluentd configmap