Issue #2536 has been updated by Nigel Kersten. Status changed from Accepted to Closed Affected Puppet version deleted (0.25.0rc1)
This would entirely break everyone using round robin DNS to load balance individual operations. Can you not configure your local cache node-side to achieve this? ---------------------------------------- Feature #2536: Cache Puppet server IP https://projects.puppetlabs.com/issues/2536 Author: Christian Hofstaedtler Status: Closed Priority: Normal Assignee: Category: network Target version: Statler Affected Puppet version: Keywords: Branch: Seems like currently the IP associated with the puppet server name is not cached on the client, but gets queried again from DNS all the time during a client run. Ideally, I think, the client should resolve the name when starting a run, and cache the IP until the run is complete. As I've only noticed on our production systems, I'm setting targeting this report against 0.24.5. Maybe this is already fixed in newer versions, but I didn't find a ticket for it. -- 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.
