On Thu, Aug 22, 2019 at 3:31 PM Zolvaring <[email protected]> wrote: > > I don't know why the Ansible playbook would respond differently to the host > key unless it's not running as the same user that you ssh with, so someone > else will hopefully answer that but what I can suggest if you're willing to > forego host key checking you can run the play with 'export > ANSIBLE_HOST_KEY_CHECKING=False', there is also an option for this you can > set in the configuration file. Obviously you can also try ssh-keyscan and see > if the host keys are different from your known hosts file, but the env var > will skip that check altogether (obvious security implications) > What I have been doing for now is running it as
ANSIBLE_HOST_KEY_CHECKING=False ansible-playbook -vvv network.yml --limit uranus which is still not what I want to do but it is slightly better than just exporting the variable for all to fondle. > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/7b990313-7b47-47a0-b494-23c973417a1c%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAHEKYV4XoEAeWpSEK%3D7FaHVtnRDMzpKEiH9s-fA0t3inZ4_LdQ%40mail.gmail.com.
