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 It looks like the puppet agent was sent a kill signal at one point: Feb 11 11:31:25 node1 puppet-agent[1333]: Caught TERM; calling stop This could explain why an update to /etc/hosts failed to occur — the agent was stopped before flushing changes to that file. Are you regularly killing or restarting agent daemons during their runs? 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/groups/opt_out.