Bug 1677351

Summary:	cluster-logging-operator creates cluster logging in multiple namespaces when deployed via OLM
Product:	OpenShift Container Platform	Reporter:	Jeff Cantrill <jcantril>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, rmeggins
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 10:44:00 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:

Description Jeff Cantrill 2019-02-14 15:43:33 UTC

Because of the way CLO is deployed via OLM, it is configured to watch all namespaces which allows deployments of CL in undesired namespaces.  We must restrict CL to 'openshift-logging'.

Comment 1 Jeff Cantrill 2019-02-19 16:45:01 UTC

Lowering priority as this will be resolved by proper use of OperatorGroups

Comment 2 Jeff Cantrill 2019-02-20 16:32:49 UTC

https://github.com/operator-framework/community-operators/pull/85

Comment 3 Anping Li 2019-03-08 07:14:12 UTC

Fixed in 4.0.0-0.nightly-2019-03-06-074438

Comment 6 errata-xmlrpc 2019-06-04 10:44:00 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-2019:0758