Bug 1929419 - Log forwarding API with multiple outputs same secret cause issues
Summary: Log forwarding API with multiple outputs same secret cause issues
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.6
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: 4.6.z
Assignee: Jeff Cantrill
QA Contact: Qiaoling Tang
URL:
Whiteboard: logging-core
Depends On: 1890072
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 20:37 UTC by Jeff Cantrill
Modified: 2022-05-05 18:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
* Previously, the fluentd collector pod went into a crash loop when the ClusterLogForwarder had multiple outputs using the same secret. The current release fixes this issue. Now, multiple outputs can share a secret. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1929419[*1929419*])
Clone Of: 1890072
Environment:
Last Closed: 2021-03-30 16:54:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 926 0 None open Bug 1929420: ClusterLogForwarder with Output.Secret causes fluentd crash loop 2021-03-01 21:08:11 UTC
Red Hat Product Errata RHBA-2021:0954 0 None None None 2021-03-30 16:55:09 UTC

Comment 1 Jeff Cantrill 2021-03-22 14:06:18 UTC 
Moving to Modified as PR was merged
Comment 4 Qiaoling Tang 2021-03-24 03:01:05 UTC 
Verified with clusterlogging.4.6.0-202103202154.p0
Comment 7 errata-xmlrpc 2021-03-30 16:54:58 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.23 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:0954
Note You need to log in before you can comment on or make changes to this bug.