Bug 1929413

Summary:	ClusterLogForwarder does not honor Output Secret Spec
Product:	OpenShift Container Platform	Reporter:	Jeff Cantrill <jcantril>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED NOTABUG	QA Contact:	Anping Li <anli>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.6	CC:	aos-bugs
Target Milestone:	---
Target Release:	4.6.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:		Environment:
Last Closed:	2021-02-19 15:26:18 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 Jeff Cantrill 2021-02-16 20:22:48 UTC

Description of problem: 
The ClusterLogForwarder allow a user to specify the name of a secret to use when connecting to a given output. The conf generation code ignores the secret name and assumes a secret exists that is names the same as the output


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


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

CLF generates configuration to utilize the spec'd secret name


Additional info:

Comment 1 Jeff Cantrill 2021-02-16 20:51:28 UTC

5.0 fixed here https://github.com/openshift/cluster-logging-operator/pull/895

Comment 3 Jeff Cantrill 2021-02-19 15:26:18 UTC

Closing NOTABUG as change is not required