Bug 1685768

Summary:	Servicemonitor object for fluentd isn't created when using community-operators to deploy logging.
Product:	OpenShift Container Platform	Reporter:	Qiaoling Tang <qitang>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED DUPLICATE	QA Contact:	Anping Li <anli>
Severity:	high	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:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-06 14:17:01 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 Qiaoling Tang 2019-03-06 01:46:30 UTC

Description of problem:
Deploy logging via community-operators, check servicemonitor object, only 
monitor-elasticsearch-cluster create, no object for fluentd.

$ oc get servicemonitor
NAME                            AGE
monitor-elasticsearch-cluster   24m

Version-Release number of selected component (if applicable):
4.0.0-0.nightly-2019-03-05-065158

How reproducible:
Always

Steps to Reproduce:
1.Deploy logging via community-operators
2.check servicemonitor object in logging namespace
3.

Actual results:
Servicemonitor object for fluentd isn't created along with logging stack

Expected results:


Additional info:

Comment 1 Jeff Cantrill 2019-03-06 14:17:01 UTC

Closing as duplicate.  The fact is we can't get metrics and part of that is OLM does not use the manifest so we need the operator to create a servicemonitor.  There isn't a need to introduce another issue.

*** This bug has been marked as a duplicate of bug 1683359 ***