Agent run fails after enabling package data collection (“package_inventory_d”) in Puppet 4.0 and later 📍
Agent side functions
Ensure that fact-based classification and automation work as expected by uploading facts to the primary server in Puppet 6.5 to 6.10.1📍
Identifying nodes where the Puppet daemon is enabled or disabled📍
Increase the log level to debug on Windows and *nix agent nodes in Puppet📍
Links to Puppet agent information
Resolve "Error: Evaluation Error: Empty string title at 0\. Title strings must have a length greater than zero." in Puppet📍
Resolve Puppet run failures with "(SystemStackError) stack level too deep" errors for Puppet 4.10 and later 📍
Use a task to enable or disable the Puppet daemon for a group of agents in Puppet 5.0 and 6.0📍
Use Bolt to install Puppet agent on different platforms at the same time📍

See more

Agent side functions

Claire Hernandez

September 01, 2021 17:30
Updated

Did this solve your problem?

0 out of 0 found this helpful

Puppet 6 introduced deferred functions, a new feature that allows you to run code on the agent side during enforcement. This is both functionality that people have been requesting for ages and also behavior that many people already mistakenly assumed existed. As a matter of fact, the Puppet execution model isn't very well understood at all and many people already think they're using Puppet like a shell script engine!

Comments

0 comments

Please sign in to leave a comment.