Dear Puppeteers, I'm in desperate need of help. Here's the story:
When I boot up new machines, they have a default puppet.conf which causes them to talk to our production puppetmaster at puppet.digg.internal. Some of these machines are destined for our development environment, and there is a custom fact 'digg_environment' that the default config uses to pass out an updated puppet.conf file. For these development machines, this file points server= to puppet.dev.digg.internal, which has a node block for the machine that then has their full configuration. This all seemed to work great until recently, and I'm not sure what changed. Now, what happens is that the machine boots with the default puppet.conf. It talks to the production puppetmaster, and downloads the correct puppet.conf which points server= to puppet.dev.digg.internal. In the logs, I see the "Reparsing /etc/puppet/puppet.conf" message. The report ends up getting sent to the development puppetmaster (puppet.dev.digg.internal). However, on subsequent runs, puppetd continues to talk to the production puppetmaster instead of getting it's config from the development puppetmaster! After a manual restart of the daemon, it works as expected. However, manual steps are a big bummer! The only change I can think of here is that we switched to Debian Lenny. Puppet version is 0.24.8. Any help would be appreciated! Thanks, Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
