Hey thanks for the Ansible playbook here. When attempting to execute the example provided on the README page it seems there is an unnecessary comma within the YAML playbook syntax.
This comma ends up getting inserted into an Elasticsearch configuration file, and in turn causes Elasticsearch to choke when starting up with an error like below:
java.lang.IllegalArgumentException: Failed to parse value [True,] cannot be parsed to boolean [ true/1/on/yes OR false/0/off/no ]
You'll know you're having the issue when you execute the sample playbook and it will hang on the task for:
TASK [elastic.elasticsearch : Wait for elasticsearch to startup]
Removing the comma from the playbook seemed to resolve the issue for me. Hope this helps someone else.
Hey thanks for the Ansible playbook here. When attempting to execute the example provided on the README page it seems there is an unnecessary comma within the YAML playbook syntax.
This comma ends up getting inserted into an Elasticsearch configuration file, and in turn causes Elasticsearch to choke when starting up with an error like below:
You'll know you're having the issue when you execute the sample playbook and it will hang on the task for:
Removing the comma from the playbook seemed to resolve the issue for me. Hope this helps someone else.