--
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 ansible-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Is there are problem I need to help with above?FYI, if set, ANSIBLE_HOST_KEY_CHECKING=no also passes along StrictHostKeyChecking=no as well, so there's no extra reason to define it in ansible.cfg or SSH config if you don't want to.
--
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 ansible-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
That SO is a old bug with hashed hosts that should no longer apply in recent versions of Ansible.We can and do fork once host keys are accepted so there's no need for a warning.Also Ansible already reads in ssh_config, so you can just put that setting there if you like.
--
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 ansible-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I believe the initial iteration through the hosts is single-threaded, as that occurs before the forks are created, however can you demonstrate that your configuration is causing single-threaded behavior after the forks are running?
"The point is that I'm specifically asking ansible to run concurrently using --forks, and it can't, but it doesn't let me know about the problem."This self resolves after you approve the hosts.
--
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 ansible-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Ok, so I understand now.Because we do *not* see it in known hosts *AND* you have host key checking enabled globally in Ansible but not disabled for these specific hosts, the locking code is anticipating a question from SSH will engage in anticipation of needing to block for these hosts.The answer seemst o be making an inventory variable that allows disabling host key checking on a per inventory basis.
It wouldn't be able to tell what your SSH client would do in advance, but could easily not check for that particular host.I disagree entirely that --forks should be disabled with unknown host keys, as that's simply not true -- most users will just approve the hosts they need.
However, I'm ok with being able to turn them off for a particular group, which you could set for the ec2_tag_foo group.
--
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 ansible-proje...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5932d737-feef-4124-8895-f31c5d85d59b%40googlegroups.com.
--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/442e3412-fac2-4b3b-8672-a54c78f1476f%40googlegroups.com.
--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/a828f04b-369e-4b75-acb2-522903aadbe0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/feb40220-6a8b-4813-826d-5447e9f1b3a8%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/c6313bab-23a5-4f5b-874c-826fdd029ace%40googlegroups.com.
Vincent, I now use a slightly different workaround. Instead of routing known_hosts to /dev/null I route it to a temp file. This keeps the EC2 noise out of my default known_hosts file, and seems to play well with ansible.
From my ~/.ssh/config file:
Host *.amazonaws.com
PasswordAuthentication no
StrictHostKeyChecking no
UserKnownHostsFile /tmp/ec2_known_hosts
User ec2-user
Hope that helps you.
-- Mike
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAMFyvFiYHSn8GF_kMNx6ea70z7RV%2ByRoGQd%2B8M-%2BSZ0AMC4%3DSQ%40mail.gmail.com.
--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/550bdafe-2892-477b-9452-bbed389bfbce%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/aa3c8257-cb5c-40b1-94fc-051fee1748fc%40googlegroups.com.
Dear all!
I'm in the process of exploring ansible and already found it pretty cool.
There is one thing, however, which I could not figure out: parallel execution.
I have a simple play:
- hosts: all
# serial: 5
tasks:
- name: parallel
command: sleep 10
Which I try to run with 'ansible-playbook -f 20 -i infra ./paralell-test.ymll'
It seems that the commands are executed in sequential order on all hosts set in the inventory, independently if I give or set the -f or the serial: parameter.
Any clues how to enable parallel task execution?
I'm using 1.2.1.
Thanks!