Upgrade your agents as new versions of Puppet Enterprise become available. The puppet_agent module helps automate upgrades, and provides the safest upgrade. Alternatively, you can upgrade individual nodes using a script.
Upgrade *nix or Windows agents using the puppet_agent module
The puppetlabs-puppet_agent module, available from the Forge, enables you to upgrade multiple agents at once. The module handles all the latest version to version upgrades.
When upgrading agents, first test the upgrade on a subset of agents, and after you verify the upgrade, upgrade remaining agents.
After the Puppet run, you can verify the upgrade with /opt/puppetlabs/bin/puppet --version
Upgrade a *nix or Windows agent using a script
To upgrade an individual node, for example to test or troubleshoot, you can upgrade directly from the node using a script. This method relies on a package repository hosted on your master.
/opt/puppetlabs/puppet/bin/openssl version
and the agent's version with openssl version
.Upgrade a *nix agent using a script
You an upgrade an individual *nix agent using a script.
- Configure the master to download the agent version you want to upgrade.
- SSH into the agent node you want to upgrade.
- Run the upgrade command appropriate to the operating system.
- Most
*nix
/opt/puppetlabs/puppet/bin/curl --cacert /etc/puppetlabs/puppet/ssl/certs/ca.pem https://<MASTER HOSTNAME>:8140/packages/current/install.bash | sudo bash
-
Mac OS X,
Solaris, and
AIX
curl --cacert /etc/puppetlabs/puppet/ssl/certs/ca.pem https://<MASTER HOSTNAME>:8140/packages/current/install.bash | sudo bash
- Most
*nix
PE services restarts automatically after upgrade.
Upgrade a Windows agent using a script
You can upgrade an individual Windows agent using a script. For Windows, this method is riskier than using the puppet_agent module to upgrade, because you must manually complete and verify steps that the module handles automatically.
<MASTER HOSTNAME>
portion of the installer script—as provided in the following example—refers to the FQDN of the master. The FQDN must be fully resolvable by the machine on which you're installing or upgrading the agent.