John, I don't believe there is any name resolution issue. Both the CentOS and Ubuntu base boxes have "192.168.33.1 puppet" in their /etc/hosts. From inside the Vagrant VM, a ping to puppet responds immediately, and a tracepath to puppet returns as quickly as I can hit enter, showing sub-millisecond results.
I'll be happy to try any other troubleshooting steps. For now, I've just inserted pluginsync=false in the base boxes' puppet.conf files. But I'll make another couple of base boxes with pluginsync=true for troubleshooting, if needed. Thanks, Kirk On Tuesday, January 8, 2013 9:25:06 AM UTC-5, jcbollinger wrote: > > > Is it possible that you have a name resolution issue? The time scale you > described is about right for a small number of name resolution timeouts > before the client falls back to a different name server or name resolution > mechanism. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/hJ_-Tm4hg1cJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
