Bug 1684376

Summary: elasticsearch couldn't be scaled up by adjust nodeCount in clusterlogging
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: LoggingAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, ewolinet, qitang, rmeggins, sponnaga
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: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:

Description Anping Li 2019-03-01 06:22:04 UTC
Description of problem:
After increase nodeCount from 1 to 3.  The nodeCount wasn't updated in CRD elasticsearch.

Version-Release number of selected component (if applicable):
quay.io/openshift/origin-cluster-logging-operator:latest

How reproducible:
always

Steps to Reproduce:
1. Deploy logging with nodeCount=1 in CRD clusterlogging
2. Update nodeCount=3
3. Check the nodeCount in CRD Elasticsearch

Actual results:
the nodeCount=1 in CRD Elasticsearch

Expected results:
nodeCount=3 in CRD Elasticsearch

Comment 2 Qiaoling Tang 2019-03-04 06:25:48 UTC
Verified in quay.io/openshift/origin-cluster-logging-operator@sha256:4d06226507b560267b1c1e8ed2b66659acc6c72a252401b833fb2c0a7dcd7ea5.

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