That seems an elastic search error, unrelated to ansible.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
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
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from
I've refreshed my cache using ec2.py --refresh-cache.
When I run ec2.py --list, it only lists the public instances. My AWS
infrastructure has three public servers (one being a jump server) and
several private ones. I was hoping to use static groups to be able to
reference my servers by data
This should be patched in 1.9 RC2.
https://github.com/ansible/ansible-modules-core/issues/967
- James
On Sunday, March 22, 2015 at 4:55:16 PM UTC-4, Will Vaughn wrote:
I am getting the same problem. Ansible seems to be iterating over each
letter in a subnet id looking for duplicate
I am getting the same problem. Ansible seems to be iterating over each
letter in a subnet id looking for duplicate letters. Not very helpful
validation. You would think unit tests would catch this before deployment,
but they probably used a string that has no duplicate letters...
On Friday,
You're missing indentation. Take a look at the examples on the module page.
Here's a good explanation: http://yaml.org/spec/current.html#id2519916
On Wednesday, 18 March 2015 19:38:02 UTC+1, Michael Bushey wrote:
I'm attempting to use the first example on page:
Hi Brian,
Play level helps (compared to task level configuration), but ideally it
would be possible to set this for the whole playbook.
On Thursday, 19 March 2015 15:19:20 UTC+2, Brian Coca wrote:
so is play level environment support enough?
--
Brian Coca
--
You received this
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
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
