On 30/11/2013 02:59, Steven Haddox wrote:
> $ time ansible-playbook provisioning/site.yml -i
> provisioning/hosts/vagrant -u vagrant -s -v
>
> Brian: I checked the sshd_config and it already has the "UseDNS no" line
> set via vagrant's tweaks itself apparently.
>
> Overall there isn't an error that's ever thrown, just a long delay
> between the "GATHERING FACTS" start time and end time before the play
> books run as expected...
Steven,
Could you compare the timings for :
time ansible <only one host> -m ping -i provisioning/hosts/vagrant -u
vagrant -s -v
and
time ansible <same host> -m setup -i provisioning/hosts/vagrant -u
vagrant -s -v
While you're doing that, it could be great to have a tcpdump running on
the vagrant machine in some other terminal, tracking network traffic :
vagrant ssh <host> "tcpdump -nviany port not 22"
Your problem really sounds like a netwprk time out issue on the vagrant
host (with DNS reverse lookup being the ususal suspect). However, I've
skimmed through setup module code and it doesn't do any DNS lookup
AFAIK... So it might be something else.
M
--
Michel Blanc
{ :github => "@leucos", :twitter => "@b9m", :gpg => "0X24B35C22" }
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
