Bug 1706134

Summary:	Specifying more than 3 nodes on Cluster Logging CR creates invalid Elasticsearch CR
Product:	OpenShift Container Platform	Reporter:	ewolinet
Component:	Logging	Assignee:	ewolinet
Status:	CLOSED CURRENTRELEASE	QA Contact:	Anping Li <anli>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	anli, aos-bugs, mburke, rmeggins
Target Milestone:	---
Target Release:	4.1.z
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-05-13 13:38:22 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 ewolinet 2019-05-03 15:56:12 UTC

Description of problem:
Currently, if you specify more than three nodes for the Cluster Logging Operator to create/manage it creates an Elasticsearch CR with a data master client node of X replicas. In the Elasticsearch Operator any configuration with more than three (3) master nodes is considered invalid and will not create any nodes.

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

How reproducible:
Always

Steps to Reproduce:
1. With Logging operators installed -- create an ClusterLogging CR with more than 3 nodes of type Elasticsearch (Logstore spec)
2. Observe no Elasticsearch nodes created and condition in Elasticsearch CR stating that it is invalid.

Actual results:
Condition in Elasticsearch CR status that the configuration is invalid for more than 3 masters. No Elasticsearch nodes are created.


Expected results:
A configuration is provided that allows for X data nodes to be created.

Additional info:

Comment 1 ewolinet 2019-05-03 16:51:28 UTC

https://github.com/openshift/cluster-logging-operator/pull/168

Comment 2 ewolinet 2019-05-06 22:27:55 UTC

https://github.com/openshift/cluster-logging-operator/pull/170

Comment 4 Anping Li 2019-05-08 04:47:31 UTC

Verified with openshift/ose-cluster-logging-operator:v4.1.0-201905071513

Comment 5 Anping Li 2019-05-09 01:04:16 UTC

@Michael, The document should be updated accordingly.

Comment 6 Michael Burke 2019-05-09 17:21:44 UTC

Eric and Anping --

Is it the Elasticsearch Operator that must be 1 or 3 nodes? I seem to recall that requirement somewhere.

Comment 7 Michael Burke 2019-05-09 17:22:40 UTC

PR: https://github.com/openshift/openshift-docs/pull/14795

Added:
Specify `1` or `3` Elasticsearch nodes. Any configuration with more than three Elasticsearch nodes is considered invalid and no nodes are created.

Comment 8 ewolinet 2019-05-09 21:19:15 UTC

Michael, I believe you're thinking of the number of master nodes that there should be in the cluster for a quorum.
The elasticsearch operator handles that

Comment 9 Michael Burke 2019-05-09 21:27:11 UTC

Changed to "Specify the number of Elasticsearch nodes, maximum of `3`. Any configuration with more than three Elasticsearch nodes is considered invalid and no nodes are created."

Comment 10 ewolinet 2019-05-10 13:50:26 UTC

@Michael that is incorrect though, this bug resolved that.