Hi! I'm trying to install a single-node ES instance on Debian GNU/Linux 9.4 (stretch) using the Ansible role and I see the play hanging in the following task (appears to execute the first item (the old APT repo) and never gets to the second item (new APT repo)):
I have the verbose output from the run of this particular task and result (the first item in the list) until it is interrupted with Ctrl-C here: https://pastebin.com/xHyS9zTt
Right now the ansible-elasticsearch role is only being tested with Ubuntu 14.04, 16.04, Debian 8 and Centos 7. I'm going to try and run this locally with Debian 9 to see if this should be working or not. I'll also make sure this lands in the automated pull request testing job.
Yep, the package installs fine and starts up and runs. In fact from the playbook it worked if I commented out completed items from the loops and let it creep forward one at a time (package installed and could be configured and started fine).
I ran into the same issue elsewhere in the playbook after manually passing through some of the loop items in the tasks, so it's not specific to what I initially reported. I also don't think it's related to the playbook at all, something specific to my environment more likely. I'm running ansible 2.5.2 on Python 2.7.14 on OpenBSD amd64 and haven't noticed any behavior like this in any playbooks before the 2.5.x update to Ansible.
+1 for idea of adding to automated tests, the Ansible playbook option is very welcome and it would be great for it to be available/reliable going forward.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.