On Sun, Aug 21, 2011 at 10:15 PM, Nan Liu <n...@puppetlabs.com> wrote: > > On Sun, Aug 21, 2011 at 7:53 PM, Khoury <khoury.bra...@gmail.com> wrote: > > Adding the entry "127.0.0.1 <non-fqdn-hostname>" solved the > > problem. I suppose that means dns/reverse dns is one of the ways that > > puppet determines what the node name is (although in my case it > > appears to be inconsistently applied). I'm just going to make sure the > > entry is in each host file using puppet. A bit annoying but > > manageable. It would be nice if there were an option under [agent] to > > set how it determined the node name though. > > Try setting the option certname in the options or add it to > puppet.conf [agent] or [puppetd] section (dependent on your version). > > Thanks, > > Nan > > --
It actually randomly happened again even with that entry, but with the puppet config push I had added it to the bottom of the file instead of the top where I had it when it fixed it so I'm going to try this for sure. I'm not sure if the position of it in the file matters, but since it seems so random explicitly calling certname definitely seems like the best option. Thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
