Issue #9206 has been updated by Daniel Pittman. Status changed from Rejected to Accepted
Fun times. We really do support automatic reloading of the configuration file, right beside manually reloading with a signal. So, this should totally work. I bet it turns out that the problem is down in the heart of NSS or the Ruby Resolv library, and that we can't flush the lookup cache without a full reexec cycle for Puppet though. Just as a hint to anyone trying to fix this. ---------------------------------------- Bug #9206: Puppet agent doesn't seem to update the server option when changed in config https://projects.puppetlabs.com/issues/9206 Author: Zach Leslie Status: Accepted Priority: Normal Assignee: Zach Leslie Category: agent Target version: Affected Puppet version: 2.6.7 Keywords: Branch: I've recently changed the configuration of our puppet agents to point to a new master. Even though the configuration has changed to reflect the new master as the `server` option, the agents that have been running continue to check in to the old master. Restarting the agent on all systems has resolved the issue and all agents are now checking in with the correct master. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
