The data.path parameter shouldn't be set to an array

[Simon Pasquier]

This bug affects only the releases 0.7 and 0.8 of the Elasticsearch-Kibana plugin.

This is an example of Elasticsearch configuration file that the plugin generates:

### MANAGED BY PUPPET ###
---
bootstrap:
  mlockall: true
http:
  cors:
    allow-origin: /.*/
    enabled: true
node:
  name: node-2-es-01
path:
  data:
    - /opt/es-data/elasticsearch_data/es-01
threadpool:
  bulk:
    queue_size: 1000

The path.data parameter is set to an array value which has a subtle but important consequence for Elasticsearch < 1.7 (eg LMA 0.7 and 0.8): with these versions, Elasticsearch will continue to use /var/lib/elasticsearch as a potential data location. In general, this wouldn't be an issue because ES picks up the location that has the most free space but when /opt/es-data gets full, it will switch to /var/lib/elasticsearch and potentially fill the / partition too.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/295671

[Denis Klepikov (dklepikov)]

Please set Importance to Critical due to current behavior can fill-in root filesystem and crash the Elasticsearch server with a potential loss of data (logs).

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/295671
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-elasticsearch-kibana/commit/?id=e70326fd95630ffd35bdc6ddcfe35e8ca60b60c2
Submitter: Jenkins
Branch: master

commit e70326fd95630ffd35bdc6ddcfe35e8ca60b60c2
Author: Swann Croiset <email address hidden>
Date: Tue Mar 22 09:40:08 2016 +0100

    Specify explicitly one data.path

    Change-Id: Idb1cb203b4c81ebe592e4d532d7d6b0ff1ca8e35
    Fixes-bug: #1559126

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/0.8
Review: https://review.openstack.org/296310