Puppet read a cached version of the puppet.conf file with multiple actions running on a node such as generating a certificate and setting a parameter to noop mode. These conflicting actions caused changes to the node in Puppet Enterprise.
Version and installation information
PE version: All supported
Solution
Search for actions that trigger Puppet to run outside a scheduled run by checking the syslog in PE based on your deployment.
- Linux:
var/log/messages - Ubuntu:
var/log/syslog - Windows: Check the Windows Event Log for the Puppet agent.
To check the status of the noop parameter in PE, run: puppet config print noop.
How can we improve this article?
0 comments
Please sign in to leave a comment.
Related articles