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

Bug 1782566

Summary:	secure forward not supported unless LogForwarding TechPreview is Enabled
Product:	OpenShift Container Platform	Reporter:	Jeff Cantrill <jcantril>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, bparees, cvogel, qitang
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Introduction of LogForwarding API modified the previous manor in which fluentd was configured Consequence: The previous way to enable the feature was no longer being respected. Fix: Add a mechanism for user's to enable log forwarding in a manor that is similar to the previous enablement Result: Using forward protocol outside of LogForwarding feature is supported.	Story Points:	---
Clone Of:
Clones:	1783732 (view as bug list)		Environment:
Last Closed:	2020-05-13 21:54:51 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:
Bug Depends On:
Bug Blocks:	1783732

Description Jeff Cantrill 2019-12-11 21:01:17 UTC

Description of problem:

Per [1], forwarding to another instance of fluent is supported as a managed feature.  The introduction of the LogForwarding feature removes this option leaving customer's to either choose an unsupported tech-preview feature or make ClusterLogging unmaganged and be unsuported.  User's of CL should be able to configure forwarding as or similar to described and still be supported.

[1] https://docs.openshift.com/container-platform/4.1/logging/config/efk-logging-external.html#efk-logging-fluentd-external_efk-logging-external

Comment 6 errata-xmlrpc 2020-05-13 21:54:51 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, 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:0581