- If you’re upgrading from Puppet 3.x
- Puppet agent 1.10.8
- Puppet agent 1.10.7
- Puppet agent 1.10.6
- Puppet agent 1.10.5
- Puppet agent 1.10.4
- Puppet agent 1.10.3
- Puppet agent 1.10.2
- Puppet agent 1.10.1
- Puppet agent 1.10.0
This page lists changes to the
puppet-agent package. For details about changes to components in a
puppet-agent release, follow the links to those components in the package release’s notes.
puppet-agent package’s version numbers use the format X.Y.Z, where:
- X must increase for major backwards-incompatible changes
- Y may increase for backwards-compatible new functionality
- Z may increase for bug fixes
If you’re upgrading from Puppet 3.x
puppet-agent package installs the latest version of Puppet 4. Also read the Puppet 4.0 release notes, since they cover any breaking changes since Puppet 3.8.
Puppet agent 1.10.8
Released September 14, 2017.
This release contains a bug fix in Puppet 4.10.8 and a versioning fix in the Windows package. No other components are updated.
Bug fix: Change NSSM version increment to avoid upgrade issues
Previous versions of Puppet agent did not increment the version of NSSM in a manner expected by Microsoft Installer (MSI), leading to MSI unintentionally removing it upon upgrade. Puppet agent 1.10.8 resolves this issue by changing the versioning scheme for NSSM.
Puppet agent 1.10.7
Released September 6, 2017.
Security improvement: Enable Data Execution Prevention (DEP) support in Windows builds of pxp-agent
As part of security robustness measure, this version of the
puppet-agent package for Windows enables data execution prevention (aka /NX) and address space layout randomization (ASLR) in third-party binaries, such as Ruby and OpenSSL, that are built along with Puppet Agent modules. There was no specific known vulnerability, but this improvement prevents potential exploits using the above concerns as attack vectors.
Puppet agent 1.10.6
Released August 9, 2017.
The only component update in this Puppet agent release is Puppet 4.10.6.
These platforms have been added as of Puppet agent 1.10.6:
- Debian 9 “Stretch”
Puppet agent 1.10.5
Released July 26, 2017.
These platforms have been added as of Puppet agent 1.10.5:
- Ubuntu 16.04 (ppc64le)
- Enterprise Linux 7 (ppc64le)
- Amazon Linux 2017.03 (by using packages for RHEL 6)
Puppet agent 1.10.4
Released June 19, 2017.
This release only affects Puppet. A regression in Puppet 4.10.3 where resources created using the syntax
Resource[xx::yy] would cause an error because Puppet would not find an existing
xx::yy user defined resource type. This was caused by fixing another problem with inconsistent use of upper and lowercase in references.
Puppet agent 1.10.3
Released June 15, 2017.
This release only affects Puppet. Using ampersands (&) in custom facts was causing Puppet runs to fail in Puppet 4.10.2. This release includes Puppet 4.10.3, which resolves that issue.
Puppet agent 1.10.2
Released June 12, 2017.
Puppet agent 1.10.1
Released May 11, 2017.
An authenticated agent could make a catalog request with facts encoded in YAML. The Puppet master did not properly validate and reject the request, resulting in the server loading arbitrary objects, which could lead to remote code execution. (PUP-7483)
End of life platforms
As of the Puppet agent 1.10.1 release, we no longer ship packages for EL 4, Fedora 23, and Ubuntu 12.04.
Puppet agent 1.10.0
Released April 5, 2017.
The largest updates in this release include improvements and bug fixes for Hiera 5, which ships with Puppet 4.10.
pxp-agent new feature
pxp-agent Now responds to PXP non-blocking requests that use a duplicate transaction ID by sending a provisional response, rather than an error message. Status requests can then be sent as normal to check on the status of the original request that was duplicated. It also detects duplicate IDs that are stored on-disk, rather than only those in-memory (it no longer “forgets” when the process is restarted). (PCP-627)
pxp-agent bug fix
The default ping interval has been increased to two minutes to reduce disconnect and reconnect cycling against a heavily loaded broker. This has a side effect that failover when a connection is unavailable but the TCP connection was not properly closed now takes 4-6 minutes instead of 35-50 seconds. (PCP-729)