Puppet Server: Release Notes
This version of Puppet Server is not included in Puppet Enterprise. The latest version of PE includes Puppet Server 2.7. A newer version is available; see the version menu above for details.
For release notes on the previous version of Puppet Server, see docs.puppet.com.
Puppet Server 2.5
Released August 11, 2016.
This is a feature and bug-fix release of Puppet Server.
Potential breaking issues when upgrading with a modified
If you disabled the certificate authority (CA) on Puppet Server by editing the
bootstrap.cfgfile on older versions of Puppet Server — for instance, because you have a multi-master configuration with the default CA disabled on some masters, or use an external CA — be aware that Puppet Server 2.5.0 no longer uses the
Puppet Server 2.5.0 instead creates a new configuration file,
/etc/puppetlabs/puppetserver/services.d/ca.cfg, if it doesn’t already exist, and this new file enables CA services by default.
To ensure that CA services remain disabled after upgrading, create the
/etc/puppetlabs/puppetserver/services.d/ca.cfgfile with contents that disable the CA services before you upgrade to Server 2.5.0. The
puppetserverservice restarts after the upgrade if the service is running before the upgrade, and the service restart also reloads the new
Also, back up your masters’
ssldir(or at least your
crl.pemfile) before you upgrade to ensure that you can restore your previous certificates and certificate revocation list, so you can restore them in case any mistakes or failures to disable the CA services in
ca.cfglead to a master unexpectedly enabling CA services and overwriting them.
For more details, including a sample
ca.cfgfile that disables CA services, see the bootstrap upgrade notes.
Potential warnings when upgrading with a modified init configuration
If you modified the init configuration file — for instance, to configure Puppet Server’s JVM memory allocation or maximum heap size — you might see a warning during the upgrade that the updated package will overwrite the file (
/etc/sysconfig/puppetserverin Red Hat and derivatives, or
/etc/default/puppetserverin Debian-based systems).
The changes to the file support the new service bootstrapping behaviors. If you don’t accept changes to the file, you might see a
Service ':PoolManagerService' not foundor similar warning. To satisfy this warning, make sure the
BOOTSTRAP_CONFIGsetting in the init configuration file is set to:
If you modified other settings in the file before upgrading, and then overwrite the file during the upgrade, you might need to reapply those modifications after the upgrade.
New feature: Flexible service bootstrapping/CA configuration file
To disable the Puppet CA service in previous versions of Puppet Server 2.x, users edited the
bootstrap.cfg file, usually located at
This workflow could cause problems for users performing package upgrades of Puppet Server where
bootstrap.cfg was modified, because the package might overwrite the modified
bootstrap.cfg and undo their changes.
To improve the upgrade experience for these users, Puppet Server 2.5.0 can load the service bootstrapping settings from multiple files. This in turn allows us to provide user-modifiable settings in a separate file and avoid overwriting any changes during an upgrade.
New feature: Signing CSRs with OIDs from a new arc
Puppet Server 2.5.0 can sign certificate signing requests (CSRs) from Puppet 4.6 agents that contain a new custom object identifier (OID) arc to represent secured extensions for use with
Aside: Trapperkeeper powers the HOCON
auth.confand authorization methods introduced in Puppet Server 2.2.0. This new CSR-signing functionality in Server 2.5.0 builds on features added to Puppet 4.6 and the addition of X.509 extension-based authorization rules added to Trapperkeeper alongside Puppet Server 2.4.
To sign CSRs wth the new OID arc via the Puppet 4.6 command-line tools, use the
puppet cert sign --allow-authorization-extensions command. See the
puppet cert man page for details. This workflow is similar to signing DNS alt names.
The new OID arc is “puppetlabs.1.3”, with a long name of “Puppet Authorization Certificate Extension” and short name of
ppAuthCertExt (where “puppetlabs” is our registered OID arc 220.127.116.11.4.1.34380). Set the extension “puppetlabs.1.3.1” (
pp_authorization) on CSRs that need to be authenticated via the new workflow. We’ve also included an default alias of
pp_auth_role at extension “puppetlabs.1.3.13” for common workflows. See the Puppet CSR attributes and certificate extensions documentation for more information.
We’ve also improved the CLI output of
puppet cert list and
puppet cert sign to work better with the
--machine-readable flags, and we allow administrators to force a prompt when signing certificates with the
This allows for easier automated failover to authorized nodes within a Puppet infrastructure and provides tools for creating new, securely automated workflows, such as automated component promotions within Puppet-managed infrastructure.
Bug fix: Unrecognized parse-opts
Puppet Server 2.4.x used a deprecated API for a Clojure CLI option-parsing library. As a result, calls to
puppetserver gem (either directly, or indirectly by using a
puppetserver_gem package resource) generated unexpected warning messages:
Warning: Could not match Warning: The following options to parse-opts are unrecognized: :flag
Puppet Server 2.5.0 updates this library, which prevents this error message from appearing.
Bug fix: Puppet Server no longer ships with an empty PID file
When installed on CentOS 6, Puppet Server 2.4.x included an empty PID file. When running
service puppetserver status, Puppet Server returned an unexpected error message:
puppetserver dead but pid file exists.
When performing a clean installation of Puppet Server 2.5.0, no PID file is created, and
service puppetserver status should return the expected
not running message.