puppet-agent package contains multiple components. Understanding how package versions are numbered and which versions go with each other is important when upgrading and troubleshooting.
Component version numbers
This table shows which components shipped in which
puppet-agent release and contains links to available component release notes. In version 6.1 and later, agent release notes are included on the same page as Puppet release notes.
| ||Puppet||Facter||Hiera||Resource API||Ruby||OpenSSL|
|6.0.6||This version of Puppet was never released.|
- This package contains Puppet’s main code and all of the dependencies needed to run it, including Facter, Hiera, and bundled versions of Ruby and OpenSSL. After it’s installed, you have everything you need to run the Puppet agent service and the
- This package depends on
puppet-agentand adds the JVM-based Puppet Server application. After it’s installed, Puppet Server can serve catalogs to nodes running the agent service.
How Puppet version numbers work
puppet-agent package distributes several different pieces of software, some of which have different version numbers. For example,
puppet-agent 6.3.0 shipped Puppet version 6.3.0, but Facter version 3.13.0 and Puppet Server 6.2.0. The
puppet-agent package doesn’t necessarily match the version of Puppet it installs.
Puppet Server is a separate application that, among other things, runs instances of the Puppet master application. It has its own version number separate from the version of Puppet it runs and may be compatible with more than one existing Puppet version.
Upgrade order is important. First, update Puppet Server, then
puppet-agent. If you upgrade Puppet Server or PuppetDB to version 5 or newer, it automatically upgrades the
puppet-agent package on the master to version 5.0.0 or newer. Puppet Server 5 also restricts you from installing anything older than
puppet-agent 5.0.0 on your agent nodes.
Master and agent compatibility
Use this table to verify that you're using a compatible version of the agent for your PE or Puppet master.
PE 3.xPuppet 3.x
PE 2015.1 through 2017.2Puppet 4.x
PE 2017.3 through 2018.1Puppet 5.x
PE 2019.0 and laterPuppet 6.x
- Puppet 3.x has reached end of life and is not actively developed or tested. We retain agent 3.x compabilility with later versions of the master only to enable upgrades.
You can use pre-6.x agents with a Puppet 6.x or PE 2019.0 or later master, but this combination doesn't take advantage of the new intermediate certificate authority architecture introduced in Puppet Server 6.0. To adopt the new CA architecture, both your master and agents must be upgraded to 6.x/2019.0, and you must regenerate certificates. If you don't upgrade all of your nodes to 6.x, don't regenerate certificates, because pre-6.x agents won't work with the new CA architecture.