Issue #2776 has been updated by James Juran.
FYI, as a workaround for this Fedora and RHEL now put /etc/NetworkManager/dispatcher.d/98-puppet in place that restarts puppet in this scenario. Of course this only helps if you're running NetworkManager. ---------------------------------------- Bug #2776: changes to resolv.conf are not followed by puppet on clients https://projects.puppetlabs.com/issues/2776#change-84552 Author: Ludwin Janvier Status: Accepted Priority: Low 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
