Troubleshooting Puppet run failures
Puppet Enterprise (PE) creates a View Report link for most failed runs, which you can use to access the run's events and logs. You might encounter these errors when a Puppet run fails.
Usually caused by conflicting classes. Check the run log to get information.
This error can also occur when running in no-op mode.
Occurs when you try to trigger a Puppet run on a node, but there is already a Puppet run in progress. This could be a scheduled run or a run started by another user.
Occurs if you attempt to start a Puppet run but the agent isn’t available.
Occurs when the run report is not successfully stored in PuppetDB after the run completes.
Some part of the request is invalid. If you used the command line or the orchestrator API to start the Puppet run, check the formatting of your command or request. If you're using the console, or your command or request is well-formed, your Puppet code might be have incorrect formatting.
You have permission to run Puppet on the node, but the agent is not responding.
