We got burned by this too. We use Ansible from a single Jenkins server to manage instances in multiple EC2 VPCs. We use strict host checking for security and we have a custom known_hosts file per VPC (we've automated updates to known_hosts on each deploy).
"Reading the SSH config to pick up the correct known_hosts locations" (option #1 posted by Matt) seems the most intuitive solution. Guess we are generally spoiled by Ansible :-) Ansible fits so well into our workflows that we assumed it would also honor our ssh configuration. And in fact Ansible mostly does honor our ssh configuration because our playbooks and adhocs do run with the custom known_hosts -- but the silent impact to performance (serial, never parallel) was unexpected. Appreciate your work! -- Steve -- 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-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/6906b847-2fe9-4fe2-bbc8-ffb870c241ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
