Issue #2776 has been updated by Ashley Penney. Affected Puppet version changed from 0.25.1 to 2.7.9
I want to bump this ticket because with 2.7.9 this is still relevant. In my environment I was relying on two nameservers and one of these was decommissioned (without anyone notifying me). I was able to correct all the nameserver lines but I noticed that none of my clients had checked into puppet overnight. I had to restart puppet on every single machine hit by this issue in order to get it to operate again. Has there been any progress in the last six months on this? I consider this to be kind of important because a DNS issue shouldn't be enough to cause puppet to fail permanently until restarted. ---------------------------------------- Bug #2776: changes to resolv.conf are not followed by puppet on clients https://projects.puppetlabs.com/issues/2776 Author: Ludwin Janvier Status: Accepted Priority: Normal Assignee: Category: network Target version: Affected Puppet version: 2.7.9 Keywords: Branch: How to reproduce : 1) Comment "nameserver" lines in your resolv.conf (or, I suppose, any DNS-resolution config on the system) 2) Start puppet demon. Of course, I get messages : puppetd[10109]: Could not request certificate: Certificate retrieval failed: Could not find server puppet puppetd[10109]: Could not find server : getaddrinfo: Temporary failure in name resolution 3) Edit resolv.conf and restore namserver lines. Puppet is not able to get its server (same lines) This is not just a paper issue. In my farms, server get their DNS config via DHCP. And parameters are written a few seconds AFTER puppet start (even if network service is started before puppet). Thus, puppet is never working on my server ; I have to restart puppet by hand. See https://bugzilla.redhat.com/show_bug.cgi?id=532085 Version : 0.25.1 -- 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.
