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

Bug 1665235

Summary:	Clarify logging-es cluster restart message
Product:	OpenShift Container Platform	Reporter:	Robert Bost <rbost>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, jokerman, mmccomas, rmeggins
Target Milestone:	---
Target Release:	3.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-20 14:11:02 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 Robert Bost 2019-01-10 18:02:34 UTC

Description of problem:

The following message is printed out sometimes:

> Cluster logging-es-ops was not in an optimal state and will not be automatically restarted. Please see documentation regarding doing a full cluster restart.

https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_logging_elasticsearch/tasks/restart_cluster.yml#L39-L50

The term cluster is overloaded here and not immediately clear if ElasticSearch or OpenShift cluster needs to be restarted. 

I understand that we intend ElasticSearch cluster here and that these docs should be referenced: 

https://docs.openshift.com/container-platform/3.11/install_config/aggregate_logging.html#elasticsearch-full-restart

Can this be clarified in the Ansible playbook message?

Comment 1 Jeff Cantrill 2019-01-10 18:50:12 UTC

https://github.com/openshift/openshift-ansible/pull/10988

Comment 3 Anping Li 2019-02-12 06:52:06 UTC

The fix is in openshift-ansible-3.11.82-1.git.0.f29227a.el7.noarch. Move to verified.

Comment 5 errata-xmlrpc 2019-02-20 14:11:02 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:0326