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
On Monday, September 29, 2014 8:37:43 AM UTC-7, Vincent Janelle wrote:
>
> Exactly like what was described at the start of this thread. :( Setting
> the environment variable produces the desired parallel execution.
>
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/550bdafe-2892-477b-9452-bbed389bfbce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
