Jira (PUP-1697) hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen commented on an issue   Re: hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode Laurence Foley I wasn't able to re-produce this behavior using a simple master/agent setup. Any new defined type instances added to the master's manifests were picked up by demonized agents on the very next catalog run. If the issue is still that the agents are not applying new host entries until restarted, could you try examining the contents of the catalog being delivered from the master? These are stored on agent nodes as JSON documents in the catalog subdirectory of the directory returned by puppet agent --configprint client_datadir. Check for objects of type "host" with a title of "apache-service" (or whatever the missing host definition happens to be named). If the missing host definitions are there, then the issue is agent-side and very strange. If the definitions are missing, then the master isn't generating an updated catalog until the agent checks in after being restarted. Add Comment   Puppet / PUP-1697 hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode The hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode. If a restart of the puppet agent is triggered, the changes are made. {code} Feb 11 11:17:59 node1 puppet-agent[5806]: Finished catalog run in 0.42 seconds Feb 11 11:20:59 node1 puppet-agent[5993]: Finished catalog run in 0.42 seconds Feb 11... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.