Agents
- Remove Windows updates from the list of available updates in Puppet Enterprise patch management
- Fix a “Could not find a directory environment” error when running “puppet resource package” in Puppet Enterprise
- Linux agent is unresponsive when started in Puppet Enterprise
- Fix a “Does the directory exist?” error in Puppet Enterprise after adding an agent node
- Puppet runs fail with a "WARNING: MSG:UnableToDownload" on Windows 2016 and earlier when using Chocolately
- Ensure that fact-based classification and automation work as expected by uploading facts to the primary server in Puppet Enterprise
- Agent runs fail on a FIPS enabled master in Puppet Enterprise 2018.1 to 2019.1
- "Pe_repo" error during Puppet runs after installing Bolt on a primary server in Puppet Enterprise
- After a Red Hat 7 OS update agents are not responding in the console in Puppet Enterprise
- "no implicit conversion from nil to integer" error in Puppet Enterprise 2018.1
- Puppet agent runs fail with a "Could not find catalog" error in Puppet Enterprise 2018.1.3
- Use a task to enable or disable the Puppet daemon for a group of agents in Puppet Enterprise 2018.1
- Identify nodes where the Puppet daemon is enabled or disabled in Puppet Enterprise 2017.3 to 2019.2
- Troubleshoot Puppet run errors and slow runs in Puppet Enterprise by adding flags
- Puppet run fails after enabling package data collection (“package_inventory_enabled”) in Puppet Enterprise
- AIX agent runs fail with facter errors in Puppet Enterprise 2016.4 to 2018.1
- Resolve the message 'The environment must be purely alphanumeric, not 'puppet-ca' on Windows nodes in Puppet Enterprise 2015.x to 2019.0
- Increase the log level to debug on Windows and *nix agent nodes in Puppet Enterprise
- Capture a .yaml file of a Puppet run for Puppet Enterprise
- Change the Puppet run log location using "--logdest" in Puppet Enterprise
- Debug message: Failed to load library 'msgpack' in Puppet Enterprise 3.2 to 2018.1