Ansible does not find your known hosts location from ~/.ssh/config on a per host basis and does read your ~/.ssh/known_hosts.
It does this because it needs to know, in advance of SSH asking, whether it needs to lock. Assume it's running at 50/200 forks and needs to ask a question interactively, that's why it needs to know. So if you are saying use known_hosts in a different file, that may be EXACTLY the problem. With host key checking on, and the data going elsewhere, it can't be found, and ansible is locking pre-emptively. On Mon, Sep 29, 2014 at 12:45 PM, Michael Blakeley < [email protected]> wrote: > I took it that Vincent was referring to my message of 2013-09-12 > <https://groups.google.com/d/msg/ansible-project/8p3XWlo83ho/Q1SflaZ9dyAJ>. > In that post I mentioned using /dev/null for the ssh UserKnownHostsFile > configuration key, scoped to Host *.amazonaws.com > > This configuration triggers single-threaded behavior from ansible because > ssh never stores any record of connecting to the EC2 hosts: not the first > time, not ever. Because known_hosts is /dev/null. > > -- Mike > > On Monday, September 29, 2014 9:30:32 AM UTC-7, Michael DeHaan wrote: >> >> So I'm confused - are you saying you are using known_hosts that are empty? >> >> This seems to be a completely unrelated question. >> >> The mention of /dev/null above seemed to be based on confusion that we >> didn't read it, not that it was actually symlinked to /dev/null. >> >> Can each of you clarify? >> >> On Mon, Sep 29, 2014 at 12:29 PM, Michael Blakeley <[email protected] >> > wrote: >> >>> 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 >>> <https://groups.google.com/d/msgid/ansible-project/550bdafe-2892-477b-9452-bbed389bfbce%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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/aa3c8257-cb5c-40b1-94fc-051fee1748fc%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/aa3c8257-cb5c-40b1-94fc-051fee1748fc%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnsWgx6xuJbQibon7%3DHMRnqOSTk6arpuqhPCDNv0E%2BoAqBHTg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
