If you used Razor in a previous Puppet Enterprise environment, upgrade Razor to keep your Puppet Enterprise and Razor versions synched.
After a Puppet Enterprise
continues to operate normally, but we recommend upgrading Razor as soon as possible to avoid unintended
Upgrade Razor from Puppet Enterprise 2015.2.x or later
Upgrading from 2015.2.x or later is a mostly automated
process that replaces the software repository, installs software packages, and migrates the
Razor database. Upgrading to 2016.2 or
later requires manual migration of any custom configuration from your config.yaml file to
parameters in the
If you’re upgrading to Puppet Enterprise 2016.2 or later and you’ve modified your
config.yaml file – for example, by
protect_new_nodes or customizing tasks, brokers, or hooks – make a note
of the modified settings.
- Upgrade the master.
Upgrade the agent on the Razor server node.
pe-razor-serverservice automatically restarts.
(Optional) If you’re upgrading to 2016.2 or later,
transfer any customized configurations to parameters in the
pe_razorclass.Note: To prevent accidentally overwriting machines during upgrade, the default for
protect_new_nodeswas changed to
truein Puppet Enterprise 2016.2 and later. If your environment and workflows rely on provisioning all new nodes, you must manually change
falseafter upgrade, then run puppet and restart the
razor --versionto verify that the upgrade was successful.