Hello, the problem was not DNS related, it was the hostname of my machines that were too long. He did solve the problem by adding this to my ansible.cfg:
control_path = %(directory)s/%%h-%%r #control_path = %(directory)s/ansible-ssh-%%h-%%p-%%r Hope this will help! Le vendredi 17 juin 2016 16:58:50 UTC+2, J Hawkesworth a écrit : > > I doubt ansible has its own dns cache. > I forget which distro it was now but a while back i used to have to > occasionally restart nscd service when I had dns problems like this. > > Hope this helps, > > Jon > > On Friday, June 17, 2016 at 2:20:55 PM UTC+1, Julien Deloubes wrote: >> >> Problem disappeared but finally reappeared after a few successful runs! >> I can always ssh on the impacted hosts. >> Don't know where to search? Is Ansible has some sort of dns cache or >> something? >> >> Le dimanche 12 juin 2016 16:57:59 UTC+2, Julien Deloubes a écrit : >>> >>> Hello, >>> i have a strange problem on Ansible 2.0, my playbook couldn't resolve >>> anymore the fqdn of my inventory. >>> I can ssh to the machines in my inventory. >>> I tried using an inventory file or specify the hosts with the -i option. >>> I can run the playbook using the ip @. >>> I'm scratching my head about what is happening, do you have any clues? >>> >> -- 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/1aa93d20-d272-4594-9112-ee6a152186f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
