Error with installing elasticsearch plugins using shell or command

[Greg Levine]

I posted the following question to SO. TIA for any guidance that you may be able to provide.

http://stackoverflow.com/questions/29190666/what-does-this-ansible-error-mean

[Brian Coca]

That seems an elastic search error, unrelated to ansible.


--
Brian Coca

[Greg Levine]

It is an elasticsearch error, but I'm not sure it's unrelated to Ansible. Reading the elasticsearch source, it looks like elasticsearch looks for a resource to load called elasticsearch.yml. It looks in a few places, but my suspicion is that it finds this file in $PATH. So does Ansible add playbooks to $PATH?

Elasticsearch will look in the current working directory for elasticsearch.yml. However, I'm skeptical that this is the reason because I'm running a script that loads the playbooks and calls ansible-playbook on them. When I'm running my script, I'm not running it from the same directory where the playbooks are located. And my script doesn't cd into the playbooks directory or add the playbooks directory or any playbooks to $PATH. So unless, Ansible cd's into the playbooks directory, the $PATH scenario is more likely. It's entirely possible, but I have my doubts that Ansible is changing directories since it doesn't seem necessary.

[Greg Levine]

But it looks like I'm wrong. In my script, prior to calling ansible-playbooks, I've printed pwd. It is not the directory containing the playbooks.

In the elasticsearch playbook, I've captured the value of pwd and printed it using the debug module. The current directory is now the directory containing the playbooks. Ansible is changing directories.

I'm not saying this is a bug, but it certainly has the affect of unintended consequences. Sure, I can change the name of my playbook to work around it. But I have to image it's avoidable by Ansible.

[Greg Levine]

In case anyone comes across this post, make sure you read the SO post.

https://stackoverflow.com/questions/29190666/what-does-this-ansible-error-mean

One answer is to simply change the playbook filename. But if that is not an option, you can use the chdir feature to force Ansible to move out of the playbooks dir before installing plugins.