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?
https://github.com/openshift/openshift-ansible/pull/10988
The fix is in openshift-ansible-3.11.82-1.git.0.f29227a.el7.noarch. Move to verified.
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