Puppet release notes

Review the release notes to learn about new features, resolved issues, and deprecations in Puppet. Release information is provided for Puppet Core and its predecessor, open source Puppet.

Important: Before you install a product, review the security and vulnerability announcements at Security: Puppet's Vulnerability Submission Process. The Perforce CVE list includes only zero-day CVEs in code or components developed and maintained by Perforce. These CVEs directly impact the Perforce products for which CVE data is published.
Important: Before you upgrade from open source Puppet to Puppet Core, see Upgrading from open source Puppet to Puppet Core.

Puppet Core 7.35

Released February 2025. This release introduces a new proprietary product, Perforce Puppet Core, and includes a security update.

Introducing Puppet Core

This release marks the introduction of Perforce Puppet Core, an enterprise-ready platform built on the foundations of open source Puppet. Puppet Core is developed, maintained, and supported by the Puppet business unit of Perforce Software, Inc.

Open source Puppet remains available but is no longer maintained by Perforce. For the latest open source Puppet 7 documentation, see Open source Puppet 7.34.0. If you are using open source Puppet in a production environment, consider transitioning to Puppet Core so that you can take advantage of the latest features, fixes, and security updates.

When you purchase Puppet Core, you can implement the platform in a production environment with an unlimited number of nodes. You can install Puppet agent on all supported operating systems (except for any new versions introduced in the latest release). You are entitled to the following additional benefits:
  • Professional Services assistance to install and configure Puppet Core
  • The ability to open Support tickets to address security vulnerabilities and defects
  • Support services guaranteed by a service-level agreement (SLA)
  • Entitlement to the Security Compliance Enforcement modules

Purchasing Puppet Core

See Purchasing Puppet Core.

Installing the product

For instructions, see Installing Puppet.

Upgrading the product

To transition from open source Puppet to Puppet Core, see Upgrading from open source Puppet to Puppet Core.

Security

Updated REXML

The REXML gem was updated to 3.3.9 in Ruby 2.7 and Ruby 3.2 for CVE-2024-49761.

PA-7106

Evaluated CVEs

The Puppet team has evaluated CVE-2025-0167, CVE-2025-0665, and CVE-2025-0725 and determined that the vulnerable path is not present in the Puppet Core platform. Therefore, Puppet Core is not impacted by these vulnerabilities.

Resolved issues

An update was introduced to ensure that users are aware of the Puppet Serialized Object Notation (PSON) deprecation when planning an upgrade. Because Puppet 8 removed support for PSON, users who upgraded to Puppet 8 without awareness of the change sometimes experienced failed Puppet runs. To increase user awareness, PSON deprecation notices are now logged at the default NOTICE level instead of the INFO level.

PE-40352

The semantic_puppet version is bumped. This release bumps the semantic_puppet version to 1.1.1 to fix a typo in a method name.

Puppet 7.34.0

Released October 2024. In this release, support is added for Debian 12 (Bookworm) amd64 on Puppet Server and PuppetDB, and several updates are implemented to address security vulnerabilities.

GitHub releases

Additional details about release updates are available on GitHub. For more information, go to the following sites:

Security

Patch Curl in agent-runtime

Patched Curl to address CVE-2024-8096.

PA-6961

Update libxml2

Puppet agent's vendored libxml2 is upgraded to version 2.13.4 to address the following vulnerabilities: CVE-2024-25062, CVE-2024-34459, and CVE-2024-40896.

PA-6973

Update Ruby 2.7

Ruby 2.7 was updated to address CVE-2024-27281.

PA-7089

Contributors

The Puppet team appreciates all Puppet Community members who contributed content to the October 2024 releases.

Puppet 7.33.0

Released September 2024. This release resolves an issue with catalog downloads and addresses security vulnerabilities.

GitHub releases

Additional details about release updates are available on GitHub. For more information, go to the following sites:

Security

Update REXML

The REXML gem was updated to version 3.3.6 to address the following security vulnerabilities: CVE-2024-41946, CVE-2024-35176, CVE-2024-41123, CVE-2024-39908, and CVE-2024-43398.

PA-6682, PA-6881, PA-6507, PA-6736, PA-6901

Patch RDoc vulnerability

Patched a vulnerability in the RDoc gem as distributed in Ruby 2.7.8 to address CVE-2024-27281.

PA-6282

Patch Curl in agent-runtime

Patched Curl to address CVE-2024-7264.

PA-6878

Update OpenSSL

OpenSSL was updated to address CVE-2024-5535.

PA-6889

Resolved issues

Resolved issue with catalog download.

Addressed an issue where catalog download would fail when running the puppet catalog download command with the default options. The puppet catalog download command now correctly sends facts to download the catalog. Community member nabertrand submitted this issue.

PUP-12046

Contributors

The Puppet team appreciates all Puppet Community members who contributed content to the September 2024 releases.

Puppet 7.32.1

Released July 2024. This release adds support for the following operating systems: AlmaLinux 9 (x86_64, AARCH64), Rocky Linux 9 (x86_64, AARCH64), and Ubuntu 24.04 (x86_64, ARM).

GitHub releases

Additional details about release updates are available on GitHub. For more information, go to the following sites:

Enhancements

New operating systems

You can now install Puppet agent on the following new operating systems:
  • AlmaLinux 9 (x86_64, AARCH64)
  • Rocky Linux 9 (x86_64, AARCH64)
  • Ubuntu 24.04 (x86_64, ARM)

Security

StringIO vulnerability

Patched a vulnerability in the StringIO gem as distributed in Ruby 2.7 to address CVE-2024-27280.

OpenSSL vulnerability

Addressed CVE-2024-4741 to correct an OpenSSL issue.

Reverted change

Change related to splay limits was reverted.

In the Puppet 7.31.0 release, a defect was corrected to ensure that any splay setting updates in the Puppet configuration file (puppet.conf) would be applied to daemonized Puppet runs. However, the fix resulted in an unexpected side issue that caused splays to be frequently recalculated, potentially delaying Puppet startup times. For this reason, the change was reverted. In the Puppet 7.32.1 release, splay setting updates in the Puppet configuration file (puppet.conf) are not applied to daemonized Puppet runs.

Resolved issues

Sensitive values returned by deferred functions are protected.

Previously, in certain circumstances, when a function of the Deferred type returned a value of the Sensitive type, the value was displayed in clear text. The issue is resolved to help ensure that sensitive values are protected.

Windows agents now run as expected.

Previously, when a value of 0 was specified for the runinterval setting, Windows agents ran every 30 minutes. Now, a setting of 0 causes the agents to run continuously as expected.

Resolved issue with catalog compilation.

Addressed an issue where catalog compilation would fail when running the puppet lookup command with the --compile option when server facts were present in the catalog.

Resolved issue to ensure that the Puppet agent service starts automatically.

In certain circumstances, when Puppet was successfully installed or upgraded on Microsoft Windows Server 2019 or 2022, the Puppet agent service did not restart automatically as expected. This fix helps to ensure that the service starts running without user intervention. Community member rismoney submitted the issue, which was fixed by another community member, vibe.

Contributors

The Puppet team appreciates all Puppet Community members who contributed content to the July 2024 releases and extends special thanks to the following first-time contributors: @jiwonaid and @jordanbreen28.

Puppet 7.32.0

Puppet 7.32.0 was not released because of tagging issues.

Puppet 7.31.0

Released June 2024. This release introduces support for new operating systems.

GitHub releases

Additional details about release updates are available on GitHub. For more information, go to the following sites:

Facter

Puppet

Puppet Agent

Puppet Runtime

Enhancements

New operating systems

You can now install Puppet agent on the following new operating systems:
  • Amazon Linux 2 (aarch64)
  • Fedora 40 (x86_64)
  • Red Hat Enterprise Linux 9 for Power (ppc64le)

Security

CVE-2024-2511 and CVE-2024-27282

Two security fixes are backported to 7.31.0. The fixes address CVE-2024-2511 and CVE-2024-27282.

Contributors

The Puppet team appreciates the Puppet Community members who contributed content for recent releases and extends special appreciation to these first-time contributors: anhpt37, Animeshz, garrettrowell, smokris, tlehman, and yakatz.

Resolved issues

Fixed issue with splay limits

An issue was corrected to ensure that any splay setting updates in the Puppet configuration file (puppet.conf) are applied to daemonized Puppet runs.

Puppet 7.30.0

Released April 2024.

GitHub Releases

More details about what has changed in this release are available on GitHub. Visit the following links for more information:

Facter

Puppet

Puppet Agent

Puppet Runtime

Enhancements

Option to disable catalog messages

Added a boolean Puppet setting to disable "notice" level messages specifying which server the agent requests a catalog from and which server actually handles the request. Catalog messages are enabled by default. PUP-12023

package: pacman provider: Add purgeable feature

Added an option to the pacman provider to purge config files. This feature was contributed by community member bastelfreak.

Update core modules

Updated all core modules. In particular, this update includes:
  • Removal of concurrent-ruby as a dependency
  • Support for Amazon Linux

Resolved issues

Non-literal class parameter types need to be deprecated.

Previously, non-literal class parameters caused errors due to the different default values of the strict setting. puppet parser validate also returned non-zero exit codes. Now the issue is a language deprecation, so a warning is generated and puppet parser validate returns 0. All language deprecation warnings can be disabled by setting disable_warnings=deprecations in the main section of puppet.conf. PUP-12026

Package provider "pip" not fully functional with network urls on Ubuntu 22.04.

Puppet's pip package provider now supports installing python modules via network URLs, e.g. source => 'git+https://github.com/<org>/<repo>.git'. Fix contributed by community member smokris. PUP-12027

Provider dnfmodule prompts user to trust gpg key when performing module list.

Added assumeyes option to dnf module list. Fix contributed by community member loopiv.

Puppet resource returns zero if it fails to make changes

Added new --fail command line flag for Puppet resource.

Remove Accept-Encoding header on redirect

Previously, Puppet copied all request headers in an HTTP redirect, including Accept-Encoding. In some cases when HTTP compression was enabled, the response failed to decompress, then failed to parse and triggered a vague error. This change strips the Accept-Encoding headers on redirect, allowing Ruby's built-in Net::HTTP to both compress and decompress the traffic.

Accept UnaryMinusExpression as class parameter type

Previously, class parameters of the form Integer[-1] $param failed compilation, because the value -1 was lexed as a UnaryMinusExpression containing a LiteralInteger. And since the LiteralEvaluator didn't implement theliteral_UnaryMinusExpression method, the visitor called literal_XXX for each ancestor class, until reaching literal_Object, which always raises.

This adds the literal_UnaryMinusExpression method and returns -1 times the expression it wraps.

If strict is off, the issue is ignored. If strict is warning, a warning is reported, but compilation continues. If strict is error, compilation fails.

Security

Vulnerabilities in curl

Backported patches for CVE-2024-2004 and CVE-2024-2398 in curl 7.88.1. PA-6291

Vulnerability in OpenSSL

Backported fixes to OpenSSL 1.1.1 to address CVE-2023-5678. PA-6132

Puppet 7.29.1

Released March 2024.

Resolved issues

Using a negative value with the integer type assertion on a class causes a compilation error.

Previously, negative values caused a compilation errors when used with the integer type assertion on a class. This has been fixed. PUP-12024

Puppet 7.29.0

Released February 2024.

Enhancements

Debian 12 (x86_64) support

Added support for Debian 12 (x86_64). PA-5549

Debian 12 (ARM) support

Added support for Debian 12 (ARM). PA-5747
Note: Support for Amazon Linux 2023 (ARM, x86_64), Debian 11 ARM and macOS 14 (ARM, x86_64) was added in Puppet 7.28.0.

Resolved issues

Syntactically incorrect types cause nil types in Puppet::InfoService::ClassInformationService

Previously, when a type was incorrectly specified, Puppet’s class_information_service ignored the error and produced an empty type specification. Puppet now produces a warning and assigns a default type in the nil case. PUP-11981.

Puppet 7.28.0

Released January 2024.

Enhancements

Bump concurrent-ruby to 1.2.2

Bumped concurrent-ruby gem to 1.2.2. PA-5960

Bump augueas to 1.14.1 for 7.x

Updated the augeas component of puppet-agent from 1.13.0 to 1.14.1. This change was already made in the puppet-agent 8.3.0, but was not backported to Puppet 7 until now. PA-5944
CAUTION: This update changes the PubkeyAcceptedAlgorithms setting in /etc/ssh/sshd_config from a string to a list.
Example: the line 'set Settings/PubkeyAcceptedAlgorithms +ssh-rsa' in the following code block:
augeas { 'sshd_allow_rsa':
  incl    => '/etc/ssh/sshd_config',
  lens    => 'Sshd.lns',
  context => '/files/etc/ssh/sshd_config/Match/',
  changes => [
    'set Condition/Address 192.168.0.3',
    'set Condition/User user',
    'set Settings/PubkeyAcceptedAlgorithms +ssh-rsa',
   ]
}
must be changed to 'set Settings/PubkeyAcceptedAlgorithms/seq::*[.="ssh-rsa"] ssh-rsa' following this update.

Add logging of server hostnames when requesting configuration

Puppet agents now log server hostnames when requesting catalogs. PUP-11899

Add logging of which Puppet Server handled catalog requests

Puppet agents now log the FQDN name of the server that compiled the catalog. This is useful when there are multiple compilers behind a load balancer. PUP-11900

Update package & service providers for Amazon Linux 2023

Updates Amazon Linux 2023's default package and service providers to DNF and SystemD, respectively. Contributed by GitHub user vchepkov. PUP-11976

Debian 11 (ARM) support

Added support for Debian 11 (ARM).

Amazon Linux 2023 support

Added support for Amazon Linux 2023.

MacOS 14 support

Added support for MacOS 14.

Resolved issues

puppet-agent-7.25: selinux Bindings broken on RHEL9.1

Fixed an issue introduced in 7.25.0 that prevented Puppet from managing selinux if the system libselinux libraries were previous to version 3.5. PA-5632

RHEL 8 FIPS agent fails to start after upgrade to Puppet 8

Fixed an issue that prevented the RHEL 8 FIPS agent from starting after upgrading to Puppet 8. PA-5786

/opt/puppetlabs/puppet/bin/openssl fails to load library dependencies on AIX

Set RPATH for openssl 1.1.1 to load dependencies from Puppetlabs libdir in order to ensure that /opt/puppetlabs/puppet/bin/opensslloads its library dependencies that were shipped in the puppet-agent package. PA-5925

Puppet agent on Solaris 11 x86 fails when updated to SRU >= 57

Fixed a regression that prevented the ffi gem's native extension from loading on newer versions of Solaris 11.4. PA-5929

Resources resource type should be marked as apply_to_all

Enables resources metatype compatibility with both hosts and devices. Contributed by GitHub user seanmil. PUP-11666

"Total number of facts" warning not counting array elements

Puppet incorrectly counted array elements and hash keys when determining if the number of facts exceeded the total fact count soft limit. This has been fixed. PUP-11685

dnfmodule fails to enable module with ensure version and no default stream

Puppet can now manage dnfmodule packages with ensure values other than present such as ensure => '1.4'. Fix contributed by community member evgeni. PUP-11985

Security

Upgrade OpenSSL

Upgraded OpenSSL to 3.0.12. PA-5864

Patch Curl in puppet-runtime

Patched Curl to address CVE-2023-38546. PA-5861

Puppet 7.27.0

Released November 2023.

Enhancements

Ship FIPS compatible Java key store in fips agents

FIPS Puppet agent builds now include a FIPS-compatibile java keystore.

The following Certificate Authorities were also added and removed:
  • create Atos_TrustedRoot_Root_CA_ECC_TLS_2021:2.16.61.152.59.166.102.61.144.99.247.126.38.87.56.4.239.0.crt
  • create Atos_TrustedRoot_Root_CA_RSA_TLS_2021:2.16.83.213.207.230.25.147.11.251.43.5.18.216.194.42.162.164.crt
  • create BJCA_Global_Root_CA1:2.16.85.111.101.227.180.217.144.106.27.9.209.108.62.192.108.32.crt
  • create BJCA_Global_Root_CA2:2.16.44.23.8.125.100.42.192.254.133.24.89.6.207.180.74.235.crt
  • create Certainly_Root_E1:2.16.6.37.51.177.71.3.51.39.92.249.141.154.185.191.204.248.crt
  • create Certainly_Root_R1:2.17.0.142.15.249.75.144.113.104.101.51.84.244.212.68.57.183.224.crt
  • create DigiCert_TLS_ECC_P384_Root_G5:2.16.9.224.147.101.172.247.217.200.185.62.28.11.4.42.46.243.crt
  • create DigiCert_TLS_RSA4096_Root_G5:2.16.8.249.180.120.168.250.126.218.106.51.55.137.222.124.207.138.crt
  • delete E-Tugra_Certification_Authority:2.8.106.104.62.156.81.155.203.83.crt
  • delete EC-ACC:2.16.238.43.61.235.212.33.222.20.168.98.172.4.243.221.196.1.crt
  • delete Hellenic_Academic_and_Research_Institutions_RootCA_2011:2.1.0.crt
  • delete Hongkong_Post_Root_CA_1:2.2.3.232.crt
  • delete Network_Solutions_Certificate_Authority:2.16.87.203.51.111.194.92.22.230.71.22.23.227.144.49.104.224.crt
  • create SSL.com_TLS_ECC_Root_CA_2022:2.16.20.3.245.171.251.55.139.23.64.91.226.67.178.165.209.196.crt
  • create SSL.com_TLS_RSA_Root_CA_2022:2.16.111.190.218.173.115.189.8.64.226.139.77.190.212.247.91.145.crt
  • create Sectigo_Public_Server_Authentication_Root_E46:2.16.66.242.204.218.27.105.55.68.95.21.254.117.40.16.184.244.crt
  • create Sectigo_Public_Server_Authentication_Root_R46:2.16.117.141.253.139.174.124.7.0.250.169.37.167.225.199.173.20.crt
  • create Security_Communication_ECC_RootCA1:2.9.0.214.93.155.179.120.129.46.235.crt
  • create Security_Communication_RootCA3:2.9.0.225.124.55.64.253.27.254.103.crt
  • delete Staat_der_Nederlanden_EV_Root_CA:2.4.0.152.150.141.crt

PA-4813

Add RHEL 9 (ARM64) support

Puppet now supports RHEL 9 (ARM64). PA-4998

Add Ubuntu 22.04 (ARM64) support

Puppet now supports Ubuntu 22.04 (ARM64). PA-5050

Make split() sensitive aware

The split function now accepts sensitive values and returns a Sensitive[Array]. This change was contributed by community user cocker-cc. PUP-11429

Log openssl version and fips mode

Puppet agent now logs the openssl version along with ruby and Puppet versions when running in debug mode. PUP-11930

Resolved issues

puppet ssl clean <REMOTE CERT> clears local private key and local certificate

puppet ssl clean <argument> now prints an error that <argument> is unexpected instead of deleting the local certificate and private key. PUP-11895

100% usage of a CPU core when an exec command sends EOF

Previously, Puppet could cause excessive CPU utilization on *nix if a child process closed stdin. This has been fixed. Fix contributed by community user bugfood. PUP-11897

puppet/lib/puppet/pops/time/timespan.rb:637: warning: passing a block to String#codepoints is deprecated

Eliminated a warning when running on JRuby 9.4 and using the Timespan data type. PUP-11934

Security

Upgrade OpenSSL

Upgraded OpenSSL to 3.0.11 to address CVE-2023-4807. PA-5783

Patch Curl in puppet-runtime

Patched Curl to address CVE-2023-38545. PA-5848

Deprecations and removals

Remove TrustCor CA certs

The following CA certs were removed:
  • TrustCor_ECA-1:2.9.0.132.130.44.95.28.98.208.64.crt
  • TrustCor_RootCert_CA-1:2.9.0.218.155.236.113.243.3.176.25.crt
  • TrustCor_RootCert_CA-2:2.8.37.161.223.202.51.203.89.2.crt
PA-4809

Puppet 7.26.0

Released August 2023.

Enhancements

Upgrade hiera-eyaml to 3.4+

Upgraded the hiera-eyaml component to 3.4. PA-5633

macOS 13 support

Added support for macOS 13. PA-5420

Resolved issues

ffi and nokogiri gem use the wrong architecture when cross compiling

Fixed an issue where some gems would get built using the wrong architecture when cross compiling. PA-5666

certname with .pp in the middle doesn't pick up its own manifest

Fixed an issue where manifests with .pp in their file names were not imported. PUP-11788

The --no-preprocess_deferred option breaks deferring of Sensitive file content

It is now possible to specify the content property for file resources as containing a Deferred function that returns a Sensitive value when lazily evaluating deferred values (the default behavior in 8.x or when setting Puppet[:preprocess_deferred] false in 7.x). For example: content => Deferred('new', [Sensitive, "password"]). PUP-11846

"Sleeping" agents raise "attempt to read body out of block (IOError)"

Previously, the agent erroneously tried to read a response body after closing the connection when a Puppet server requested the agent retry. Now when the agent is told to retry, the agent waits the specified sleep duration and does not error trying to read the request body after closing the connection. PUP-11853

Security

Upgrade OpenSSL

Upgraded OpenSSL to address various vulnerabilities (CVE-2023-3817, CVE-2023-3446, CVE-2023-2975, CVE-2023-0464). PA-5699

Bump Ruby URI component for CVE-2023-36617

Patched Ruby to address a vulnerability in the URI gem (CVE-2023-36617). PA-5638

Puppet 7.25.0

Released June 2023.

Resolved issues

Removed dependency on private class Concurrent::RubyThreadLocalVar

The Puppet::ThreadLocal class no longer relies on concurrent-ruby's private Concurrent::RubyThreadLocalVar class and instead uses Concurrent::ThreadLocalVar. PUP-11723

Setting to prevent falling back to non-rich data

Before, Puppet fell back to PSON when unable to serialize to JSON. This can cause issues because rich data types cannot be serialized vis PSON. A new setting, allow_pson_serialization, allows users to turn PSON serialization on or off.

allow_pson_serialization defaults to true in Puppet 7 and false in Puppet 8. When set to false, a warning is raised when falling back to PSON. When set to true, an error is raised instead. This option affects Puppet Server's configuration management service responses as well as when the agent saves its cached catalog. PUP-10928

Security

Bump curl to 7.88.1

Upgraded the curl component from 7.86 to 7.88.1 to address several security vulnerabilities. PA-5393

Deprecations and removals

Support for macOS 10.15 removed

This release removes support for macOS 10.15 from puppet-agent. PA-5413

Support for RHEL 7 (aarch64) removed

This release removes support for RHEL 7 (aarch64) from puppet-agent. PA-5418

Puppet 7.24.0

Released April 2023.

Resolved issues

Puppet resource can't load time object to YAML

The file resource now supports puppet resource file <path> --to_yaml. PUP-11763

each, map, and filter functions are slow and buggy on jruby

Fixed an issue where the each, map, and filter built-in functions in Puppet language had poor performance and consumed unnecessary resources. PUP-11755

Enhancements

Warn if Puppet falls back to PSON

Puppet Server now logs a warning instead of debug message if it fails to serialize a catalog and falls back to PSON, which usually occurs when binary data is present in the catalog. PUP-11787

Setting to report non-versioned path to resource when using versioned dirs

When the versioned_environment_dirs setting is enabled, Puppet would previously report the full directory path to the environment after resolving symlinks as the source for resources in a catalog.

Puppet now reports the path to the resource before resolving symlinks in the environmentpath. You may revert to the previous behavior by setting the new configuration option report_configured_environmentpath to false. PUP-11691

Puppet 7.23.0

Released February 2023.

Resolved issues

Can't dig into facts when legacy facts are excluded

Catalog compilation no longer fails when using the dig function and excluding legacy facts. PUP-11717

concurrent-ruby 1.2.0 breaks Puppet

Updated Puppet to require versions of concurrent-ruby prior to 1.2. PUP-11722

fqdn_rand function relies on legacy fqdn fact

Puppet now allows disabling legacy facts when using the fqdn_rand. PUP-11752

Security

Bump nokogiri to 1.13.10

Updated the Nokogiri component from version 1.13.9 to 1.13.10, addressing CVE-2022-23476. PA-4817

Puppet 7.22.0

No release notes. This version was released as gem-only.

Puppet 7.21.0

Released December 2022.

Enhancements

Allow legacy facts to be excluded

Added a Puppet setting include_legacy_facts to control whether legacy facts are sent to puppetserver when requesting a catalog. By default, Puppet continues to send legacy facts, but it can be disabled if all puppet manifests, hiera.yaml and hiera configuration layers are modified to no longer use legacy facts. PUP-11662

Allow omission of unchanged resources from reports

With the new setting exclude_unchanged_resources, Puppet can omit data about unchanged resources from reports. This can decrease the size of reports significantly. PUP-11654

Resolved issues

Tasks are not listed when a single task in an environment has malformed metadata

Tasks containing invalid JSON metadata are skipped in the GET /tasks endpoint rather than the whole response returning 500. PUP-11683

Purging SSH keys on a user resource fails when alias is used

Catalog compilation no longer fails when using the purge_ssh_keys parameter on a user resource with an alias metaparameter. PUP-11631

puppet lookup –E does not execute the ENC

If you specify puppet lookup with an explicit environment ( --environment web ) then lookup did not call to the classifier, causing any node parameters set in the classifier to be omitted. This was because calling the classifier assigns a different environment to the node by default, returning a lookup result for a different environment than was requested. This issue has been fixed. It also affected open source (replace the word classifier with ENC). PUP-11527

Security

Bump puppet-runtime's Ruby to 2.7.7

Updates puppet-agent's Ruby to 2.7.7, addressing CVE-2021-33621. PA-4805

Update libxml2 to 2.10.3

Updates puppet-agent's vendored libxml2 from 2.9.8 to 2.10.3, which addresses CVE-2021-3541, CVE-2022-23308, CVE-2022-29824, CVE-2022-40303, and CVE-2022-40304. Also updates puppet-agent's vendored libxslt from 1.1.33 to 1.1.37, which addresses CVE-2021-30560. PA-4770

osx-10.15-x86_64 - NULL pointer dereference in Nokogiri

Updates Nokogiri to 1.13.9, which addresses CVE-2022-2309, CVE-2022-40304, and CVE-2022-40303 in Nokogiri's vendored libxml2 and CVE-2022-37434 in Nokogiri's vendored zlib. PA-4767

Puppet 7.20.0

Released October 2022.

Enhancements

Tag and bump puppet-resource_api in Puppet 7

Bumps resource-api gem to 1.8.16. PA-4702

Resolved issues

Puppet::Util::Json raises an error when reading an empty file

Puppet no longer errors when loading an empty task metadata file. PUP-11629

Augeas not working on M1 macOS Big Sur

Fixed a bug in the Augeas component of the puppet-agent platform on macOS. Contributed by Puppet community member h0tw1r3. PA-4704

Augtool packaged in puppet-agent 7.19.0 is broken

puppet-agent 7.19.0 had a broken Augeas packaged with it. This is fixed in puppet-agent 7.20.0. PA-4686

Deprecations and removals

Support for Debian 9 removed

This release removes support for Debian 9 (x86 and x86-64) from puppet-agent. PA-4576

Support for Fedora 34 and 32 removed

This release removes support for Fedora 34 and 32 (x86-64) from puppet-agent. PA-4284, PA-4269

Puppet 7.19.0

Released September 2022.

Note:

New versions of Puppet now release every six weeks rather than every four weeks.

Enhancements

Support for Fedora 36 (x86_64)

This release adds support for Fedora 36 (x86_64). PA-4668

Updated Augeas to 1.13.0

Bumped Augeas to 1.13.0 for all supported platforms except for Solaris and AIX. Those two platforms remain on 1.12.0, as Augeas 1.13.0 fails to compile due to a few readline function calls that are not on Solaris or AIX. PA-4494

Resolved issues

Puppet sends malformed PuppetDB reports with Oj

Reports sent to PuppetDB using the Oj JSON backend are now properly formatted. PUP-11620

puppet module list --render-as json does not report unmet dependencies

puppet module list --render-as json now includes information about unmet dependencies. PUP-11604

Puppet does not write SELinux labels on ZFS

Marked ZFS as an SELinux-capable filesystem. PUP-11603

Puppet::Util.safe_posix_fork fails if /proc/self is not a directory

Puppet now handles misconfigured /proc filesystems correctly. PUP-11594

Puppet on Ruby 3.1 warns about ERB passing safe_level as non-keyword argument

Puppet now passes ERB arguments as keywords. PUP-11552

Security

FIPS OpenSSL: disable c_rehash binary

Fixed CVE-2022-1292 and CVE-2022-2068. PA-4621

Puppet 7.18.0

Released August 2022.

Enhancements

Bump to openssl-fips-1.1.1k-6

Updated openssl-fips on RedHat to 1.1.1k-6. PA-4498

Update puppet-ca-bundle

Updated root certificate authority bundle included with puppet-agent. PA-4496

Support for macOS 12 (M1)

This release adds support for macOS 12 (M1). PA-4457

Support for Windows 11 Enterprise (x86_64)

This release adds support for Windows 11 Enterprise (x86_64). PA-4249

Support for Ubuntu 22.04 (x86_64)

This release adds support for Ubuntu 22.04 (x86_64). PA-4233

Resolved issues

Sub-directory names returned as task names when listing tasks from a module

The puppet/v3/tasks REST API only returns files in the tasks directory of each module and no longer includes the names of subdirectories. PUP-11539

Puppet agent --disable is ignored with cron puppet agent (splay).

Puppet agent now checks the disabled lock file after sleeping due to splay. PUP-9998

puppet-cacerts keystore is missing on Red Hat 9, SLES 15 and Ubuntu 20.04

If Puppet agent is installed, there is a java keystore file. PA-4440

Deprecations and removals

Support for Operating Systems removed

This release removes support for Fedora 32, CentOS 8, and Ubuntu 16.04. PA-4328

Security

Update puppet runtime's curl to 7.83.1

Updated runtime to fix CVE-2022-22576, CVE-2022-27774, and CVE-2022-27776. PA-4472

Puppet 7.17.0

Released May 2022.

We would like to thank the following Puppet community members for their contributions to this release: jplindquist, lollipopman, jps-help.

Enhancements

Resolve deferred values on demand instead of at catalog read time

It's now possible for deferred functions to be called on demand instead of being preprocessed. This way other resources in the catalog can serve as inputs to the deferred function. If the deferred function fails, then only that resource fails, while unrelated resources are still applied. To enable this behavior, set Puppet[:preprocess_deferred] = false or use --no-preprocess_deferred on the command line. PUP-9323

Add virt-what and dmidecode in Puppet Agent

Adds virt-what and dmidecode components to Puppet Agent. PA-4423

Nokogiri security vulnerability fix

Fix for CVE-2022-29181. PA-4489

Resolved issues

Puppet::HTTP::Client cannot connect to a server requiring client cert authentication and whose server cert is issued by a CA in the ssl_trust_store

Puppet's http client can now establish a mutually authenticated TLS connection when passing include_system_store: true such as when retrieving file content from HTTPS servers. Previously Puppet did not add its client certificate to the SSL context, so the connection would fail if the HTTPS server required a client certificate. PUP-11522

Remove compiler errors for deferred function mismatched types

Before, it was not possible to compile a catalog that used a Deferred value for a typed parameter class. The compiler would give an error message stating that the type expected did not match Deferred. Now, the compiler inspects the Deferred class's return type and ensures it matches the class parameter type. If the Deferred function has no return type, the compiler warns that it cannot guarantee whether the type adheres to the type the class specifies. PUP-11518

Yum provider does not properly update package using version range and install options

Yum provider now accepts disablerepo, enablerepo, and disableexcludes install options if a range is specified. PUP-11475

Legacy function error does not include the source ref

If a 3x function produces an error, the error message now includes the path to the file in which the function is defined. PUP-11472

Cannot login under user created by Puppet on macOS 12.1

On macOS, Puppet now validates that the salt parameter for the user resource is a hex encoded string of length 64 exactly. ​​PUP-11454

puppetserver_gem doesn't install gems when they are loaded by Facter

Fixed a bug that prevented the puppetserver_gem provider from managing gems that were first loaded by Facter. PUP-11452

Puppet Agent does not automatically refresh CRLs on crl_refresh_interval

Puppet Agent now reloads its CA and CRL bundles every 30 minutes during each run. Previously it only loaded it when the process started, which meant the service had to be restarted if the CA/CRL files changed on disk. PUP-11428

systemd: Puppet Agent starts before network-online.target is reached

Puppet Agent now waits for network-online.target and does not attempt to contact Puppet Server before having network connectivity. Previously, Puppet Agent on Ubuntu 15.04 started with a multi-user.target. If using NetworkManager with DHCP, the agent tried to apply configuration before the network connection was up, resulting in printing several errors to the logs. PUP-5402

Puppet 7.16.0

Released April 2022.

Enhancements

Allow Puppet::HTTP::Client to connect to trusted server using the puppet certificate for client authentication

You can now specify an https URL as the source of a file resource when the TLS server requires a client certificate for authentication. PUP-11471

Ruby security fix

Bumped Ruby to 2.7.6 to fix CVE-2022-28739. PA-4364

Puppet 7.15.0

Released March 2022.

Resolved issues

puppet lookup fails to interpolate topscope variables when an environment is specified

Fixed an issue where Puppet 6.26 and 7.14 failed to resolve toplevel facts in Hiera configs when using the --environment option for puppet lookup. PUP-11437

Rspec tests with custom facts fail on some modules

This release fixes an issue where rspec module tests would compile with the runner node’s facts instead of using the custom facts supplied by the test. PUP-11435

Puppet::Util::Windows is undefined on non-Windows platforms

Fixed a bug that prevented pdk unit tests from working when trying to test a resource with a Windows provider, such as "service" resources. PUP-11459

No option to fail fast when agent-specified environment does not exist

When using strict_environment_mode=true, a run now fails early if the requested environment does not exist on the server, or if the server does not allow the agent to specify its own environment. PUP-11440

Nokigiri upgrade for macOS

Upgraded nokogiri gem to 1.13.2 on macOS due to upstream security fix. PA-4323

Some gemspecs are missing from puppet-agent MSI

On Windows, it is now possible to install a gem that has a dependency on Facter or Hiera into Puppet's vendored ruby. PA-4313

Puppet 7.14.0

Released January 2022.

Enhancements

Support for RHEL 9

This release includes support for Red Hat Enterprise Linux (RHEL) 9. PUP-11364

Bump Ruby component

Upgraded Ruby component to 2.7.5. PA-4130

Resolved issues

Puppet uses deprecated psych features

Puppet is now compatible with psych 4.0. PUP-11405

Agent no longer calls the Puppet::Node terminus to resolve the environment during the run

Introduced a Puppet setting use_last_environment=true|false and a corresponding puppet agent -t --no-use_last_environment boolean command line option that forces the agent to make a node request like it did prior to 7.12 and 6.25. By default, the agent does not make a node request. PUP-11379

Puppet user and service resources are slow on Mac OS X

Managing users and services on macOS is much faster. PUP-11332

Puppet::Node#environment_name may return the wrong value

Puppet::Node#environment_name now always returns the symbolic name of the environment (if one has been set on the node). PUP-11330

Puppet lookups failed due to missing certificates

The puppet lookup command now works if the agent does not have certificates available locally. PUP-11402

Lockups on servers running in multithreaded mode

This change fixes a deadlock that occurred when running puppetserver in multi-threaded mode. PUP-11373

The generate types command does not handle errors correctly

If the generate types command failed to generate a custom type, it logged an error and returned a 0 exit code instead of failing. The command now correctly fails with a non-zero exit code if the command cannot generate a type. PUP-11078

Puppet 7.13.1

Released December 2021.

Enhancements

ENC-enforced environment bypass for lookup

You can now bypass the ENC-enforced environment when performing a lookup. To bypass the enforced environment, use lookup with the --environment option to specify the desired environment. Puppet always uses the environment you specified regardless of the ENC-enforced environment. PUP-7479

Support for Windows Server 2022

This release includes support for Windows Server 2022. PUP-11238

Resolved issues

Puppet::FileSystem.chmod does not validate its arguments

Puppet::FileSystem.chmod now validates its arguments like other methods. PUP-11345

Warning: #<Puppet::Transaction::Persistence after upgrading to Puppet agent 6.25.0

Fixes a regression introduced in 6.25.0 and 7.10.0 that caused a Puppet::Transaction::Persistence warning during each agent run. PUP-11321

User resource tries to create rather than modify users created by a utility

This release moves the ssh_authorized_key resource's creation to the end of the user type flow, after all user properties and parameters were resolved, to avoid order dependency errors. PUP-11320

Puppet code merger using incorrect command

Reduces memory usage when parsing manifests. PUP-11318

Failure when using the names "apply" and "plan" within an apply() block in a plan

The names "apply" and "plan" can now be used as resource parameter names in all cases. Previously, using them within an apply() block in a plan would fail. PUP-11315

Puppet attempts to execute directories from /etc/init.d/

Prevents Puppet from considering directories from /etc/init.d/ as services. PUP-11313

Puppet creates excessive Pathname instances

Reduces the number of Pathname allocations when parsing Puppet manifests. PUP-11312

Pathname.absolute? uses excessive memory

Backported Ruby patch to Pathname.absolute? to reduce memory usage. PUP-11311

High memory consumption from lib/puppet/pops/parser/lexer2.rb

Reduced lexer2 memory usage. PUP-11236

versioncmp() treats 11.0 as greater than 11

versioncmp() now strips redundant numbers. PUP-11235

puppet lookup --facts {filename} fails if filename does not contain a dot

Before this release, puppet lookup --facts {filename} failed early when the filename given did not contain a dot. This fix removes the early extensions check and adds a fallback instead: tries both formats (JSON then YAML) to read the given facts file when its path doesn't end with any of the expected extensions (yaml/yml/json). Otherwise, it follows previous implementation and respects the given extension. PUP-11204

Facts provided in a file cannot be used for classification

Fixed a bug where facts provided in a file were not being merged with the facts used for classification. This is because Puppet collected and merged the said facts after the classification happened. To fix this, we ensured that Puppet resolves the facts being used for classification before the node request. PUP-10435

Inconsistent handling of trusted facts in the lookup CLI

When using puppet lookup with --facts, if the facts file overrides any of hostname, domain, fqdn, clientcert, then it must override all of them. Also, if a value for certname is provided in a fact file for the lookup application, use it when creating the trusted information object. This makes it possible to override trusted.certname for classification. PUP-8220

Lookup ignores environment from the classifier when using a rule with trusted facts

Fixed an issue where trusted facts could not be used as rules for classification. This was fixed by gathering the trusted facts from the PuppetDB query result, and overriding the trusted facts context. PUP-8094

Misleading results when using --node flag in puppet lookup

Fixed an issue where puppet lookup would result in misleading results when using the --node flag. This happened because there can be cases where the target node does not have any facts cached. To avoid this, the fix implemented checks for the node facts/facts given in a fact file, and if it doesn't find any it raises an error. PUP-7362

Files starting with "~" in recursive directories are evaluated as usernames

Puppet can now manage files whose names start with tilde "~" characters. PUP-5800

Puppet could not retrieve attributes from fifo and socket files

This release allows Puppet to retrieve attributes for fifo and socket files and manage them when the given manifest has a file resource which is recursing over a given path. PUP-4045

Noop changes to file ownership generate failures if required user or group does not exist

Puppet now correctly reports when a file's owner or group would change in noop mode, even if the owner or group would be created in the same run. PUP-3907

Puppet hangs trying to replace a FIFO

Puppet no longer hangs when trying to replace a fifo with a file, directory or symlink. PUP-1460

Puppet 7.13.0

This version of Puppet was never released.

Puppet 7.12.1

Released November 2021.

Resolved issues

Puppet can leak credentials when following HTTP redirects

Previously, when Puppet followed HTTP redirects, the Authentication and Cookie headers were passed to different hosts, which could leak sensitive information. Now the Authentication and Cookie headers are only sent when redirecting to the same hosts. This fixes CVE-2021-27023. PUP-11188

Puppet agent silently skips unknown resources

Previously, all unknown resources were converted into a component (Puppet::Type::Component) by default and skipped when applying a catalog. This release adds a new resource attribute that specifies the type of resource — this is used to differentiate between built-in types and user defined types. Resources that are known and available on the server node are also verified on the agent node, which now fails when something unknown is found in the received catalog. This fixes CVE-2021-27025. PUP-11209

Note: Puppet Agent 6.25.1 and 7.12.1 introduced a new catalog resource field in order to resolve CVE-2021-27025. This field was not handled properly by older versions of PuppetDB and results in catalogs not being stored in PuppetDB. Before upgrading any agents in your installation to 6.25.1 or 7.12.1, you must first upgrade your PuppetDB(s) to this version. (PDB-5338)

Puppet gem and rspec-puppet failures

This release moves the DEFAULT_TIMEOUT constant from lib/puppet/util/windows/service.rb to lib/puppet/util/windows.rb in a non-OS guarded code area. This change avoids uninitialized constant errors when compiling catalogs on non-Windows operating systems. PUP-11319

Puppet agent downloads all plugins after updating

Puppet 6.25.0 and 7.12.0 introduced a regression which caused a newly upgraded agent to download all of its plugins. Now the agent performs a single node request to resynchronize its environment with the server. PUP-11328

Puppet 7.12.0

Released October 2021.

We would like to thank the following Puppet community members for their contributions to this release: natemccurdy.

Enhancements

Support for AlmaLinux 8 (x86_64)

This release adds support for AlmaLinux 8 (x86_64). PUP-11242

Support for Rocky Linux 8 (x86_64)

This release adds support for Rocky Linux 8 (x86_64). PUP-11231

Faster iterative functions

This release speeds up the amount of time it takes to type check arguments passed to blocks of iterative functions, such as reduce and merge. (PUP-9561)

Resolved issues

The autoloader is confused by short Windows paths

This release fixes a regression that prevented Puppet from running when the current working directory was a short Windows path (8.3). PUP-11184

Superclass mismatch causes regression

A performance patch and require_relative caused a regression on systems where Ruby paths included symlinks. This release reverts the performance patch on *nix systems. PA-4037

Default timeout ignores Windows services

Previously, default timeouts caused issues on Windows when services took longer than 10 seconds to change state. You can now specify the default timeout value for syncing service properties. PUP-10925

User attributes ignores forcelocal

This release fixes an issue where setting forcelocal => true on a user resource checked the resource's home and shell attributes against their values from the directory service provider. Contributed by Puppet community member natemccurdy. PUP-11241

Puppet fails to install packages on Solaris if another pkg install is running

Installing packages on Solaris with the pkg command does not work if another instance of pkg is already running. Now Puppet tries the install command 5 times, and only fails if the package cannot be installed. PUP-11208

The facter_interactive.bat and run_facter_interactive.bat files are missing

This release packages the missing facter_interactive.bat and run_facter_interactive.bat files on Windows. These files already existed in the repository, but they were not packaged in the MSI. PA-3700

The concat module ignores the ENC environment

This release fixes an issue where an ENC-specified environment was not pushed during a Puppet run. This caused indirector requests with no specified environment to default to using an incorrect environment. PUP-11265

Util::JSON.dump receives non-hash options

Previously, Puppet's /puppet/v3/file_metadatas REST API failed if the multi_json gem was uninstalled or when it was running puppetserver from source. PUP-11237

Puppet 7.11.0

Released September 2021.

New features

The write-catalog-summary setting

This release adds the write_catalog_summary setting to control whether the resources.txt and classes.txt files are written to disk after applying a catalog. By default, puppet agent and puppet apply behave the same as before — puppet agent writes the files, and puppet apply does not. PUP-1042

Enhancements

Support for Ubuntu 18.04 aarch64

This release adds support for Ubuntu 18.04 aarch64. PUP-11162

Lower memory consumption in Ruby files

This release lowers memory consumption by 10%. PUP-11232

Support for multiple Facter implementations

You can now register a Facter implementation when initializing Puppet via the Puppet.initialize_settings. PUP-11216

Facter.value replaced by Puppet.runtime[:facter]

This release replaces calls to Facter.value with calls to Puppet.runtime[:facter]., and removes require 'facter'. PUP-11217

OpenSSL updates

  • On windowsfips-2012r2-x64), OpenSSL 1.0.2 has been patched for CVE-2020-1971, CVE-2021-23839, CVE-2021-23840, CVE-2021-23841 and CVE-2021-3712 - PA-3976

  • On redhatfips-7-x86_64, OpenSSL has been bumped to 1.1.1k and patched for CVE-2021-3712 and CVE-2021-3711 - PA-3974

  • On all other platforms, OpenSSL has been bumped to 1.1.1l - PA-3925

Resolved issues

Puppet agent does not save local copy of last_run_report.yaml

The agent now saves a local copy of its last run report, even if it fails to submit the report to the primary Puppet server. PUP-6708

A lookup fails if lookup_options is empty

Previously, when lookup_options were defined at the global or environment layer, and the module defined an empty hash, the compilation failed. This is now fixed and the empty hash is ignored. PUP-10890

User resource not removing password on AIX agents

This release fixes an issue where deleting an AIX user with Puppet would not clean up the user's password. PUP-11190

User resource unable to remove the home directory when set to absent in AIX

This release fixes an issue where the user home directory was not removed when managehome was set to true. PUP-11170

Puppet sends warning for BOM and US-ASCII encoding

This release removes BOM for non-UTF encoding and its warnings. ASCII characters are single bytes, which means there is no need for a BOM to detect byte ordering (LSB/MSB). PUP-11196

The puppet resource --to_yaml emits class tags

This release stops the resource --to_yaml command emitting Puppet class tags, such as Puppet::Util::Execution::ProcessOutput`, by ensuring that the PScalarDataType only checks the instance of String, and not other subclasses. PUP-10105

Puppet 7.10.0

Released August 2021.

Enhancements

Scripts file serving mount

When using Puppet APIs to load file content and metadata, you can access files in the scripts/ directory of a module using the scripts file mount. PUP-11187

Load Task files from scripts

Tasks can now load files from the scripts mount. PUP-11200

Cleaned up ext/ directory

This release removes unused files from the ext/ directory used by upstream Linux and Solaris packages. PUP-10685

Exec type's onlyif and unless in --noop documented

This release documents the noop behavior of the onlyif and unless parameters of the exec resource. PUP-11199

Option to enable long filename support in the Windows MSI installer

This release updates the MSI installer for Puppet agent to enable long filenames either through a checkbox in the installer or by setting the ENABLE_LONG_PATHS=true option in the command line. PA-3843

Settings to check fact limits

Each setting has a default limit, and if that is exceeded, Puppet emits a warning message. If the default limit is set to 0, Puppet does not emit a warning. The new settings include:

  • fact_name_length_soft_limit(2560 bytes): The soft limit for the length of a fact name.

  • fact_value_length_soft_limit(4096 bytes): The soft limit for the length of a fact value.

  • top_level_facts_soft_limit(512): The soft limit for the number of top level facts

  • number_of_facts_soft_limit(2048): The soft limit for the total number of facts.

  • payload_soft_limit(16 MB): The soft limit for the size of the fact hash after its encoded. PUP-11088

RHEL9 support for services

Puppet now uses systemd as the default service provider for EL 9 variants, such as Red Hat or CentOS Stream. PUP-11168

Deprecations and removals

Support for Fedora 30 (x86_64) removed

This release removes support for Fedora 30 (x86_64). PUP-11092

Support for Fedora 31 (x86_64) removed

This release removes support for Fedora 31 (x86_64). PUP-11093

Support for MacOSX 10.14 (x86_64) removed

This release removes support for MacOSX 10.14 (x86_64). PUP-11094

Resolved issues

An environment reloaded during a single compilation could fail

Previously, Puppet Server could reload an environment while it was being used to compile a catalog. If translations were enabled (Puppet[:disable_i18n] set to false), compilation could fail. Now Puppet Server prevents environments from being reloaded while they are in use, and instead reloads the environment the next time it is requested. PUP-11158

Catalog failure on first run due to pluginsync and environment switch

Previously, an agent failed its run if it switched to a new environment where the manifests relied on a fact that only existed in the new environment. Now the agent redirects to the server-specified environment and the run continues using that environment. PUP-9570

Changes to current working directory when listing modules

Puppet Server and agent no longer change their current working directories when listing modules in an environment directory. PUP-11166

Static catalogs not working for file resources when versioned_deploys is enabled

Previously, when :versioned_environment_dirs was set to true, catalog compilation failed to add metadata for static catalog file resources; this meant that an agent receiving a catalog would not attempt to request that static file content. This has been fixed and the metadata is now correctly added to the catalog when :versioned_environment_dirs is set to true. PUP-11169

Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf

This release fixes an issue that caused the agent run to fail if the agent requested an environment that did not exist on the server ​​— even when the classifier controlled the environment. PUP-6802

Rich data types can corrupt the transaction store

This release fixes an issue that prevented Puppet from reporting corrective changes when using rich data types such as Deferred, Binary, and Sensitive. PUP-10820

Environment caches string and symbol environment names differently

This release fixes an issue that resulted in Puppet caching duplicate copies of an environment. PUP-10955

Failure to fetch node definition results in bad pluginsync and cascading failure

Previously, Puppet agents would make a node definition request to the server to find out the correct environment to run in. This request has now been removed, and the agent saves its last used environment in the last_run_summary.yaml file. If the environment is not set in the CLI or config, agents attempt to use the environment in last_run_summary.yaml — only if the previous run had an agent/server environment mismatch. PUP-10216

Puppet.lookup(:current_environment) is wrong if the environment changes during convergence

This release fixes an issue where an old environment could be used if the environment had changed due to pluginsync. PUP-10308

User resource exposes hashed password when changing password or adding a user

Previously, when managing passwords with the useradd provider, the password hash appeared when listing running processes. Now the password is set with the chpasswd command that uses stdin to receive the password from a temporary file, so it no longer appears in the process list. PUP-3634

The launchd service provider fails if a parsable but invalid LaunchAgent or LaunchDaemon plist file exists

This release fixes an issue where the launchd service provider failed if a parsable but invalid LaunchAgent or LaunchDaemon plist file exists. PUP-11164

The pkg provider cannot unhold and update package in the same run

Previously, the pkg package provider was unable to handle manifests where a package was updated and marked as unhold at the same time. This is now fixed. PUP-10956

Undefined method '[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph

Previously, the puppet module install command broke when dependencies could not be resolved. Puppet now emits an error message instead. PUP-11172

Puppet 7.9.0

Released July 2021.

We would like to thank the following Puppet community members for their contributions to this release: cocker-cc

Enhancements

Support for HTTPS as a package source

Puppet now supports installing .exe packages on Windows using HTTPS as a package source. PUP-3317

The puppet ssl show command prints custom object identifiers (OID)

The puppet ssl show command now shows the names of certificate extensions containing custom OIDs — when the trusted_oid_mapping_file exists. This functionality used to exist in the puppet cert print command. PUP-11120

Updated argument error message

If you call a function with an argument Puppet does not accept, the error message provides a list of acceptable function signatures. PUP-7792

Updated error message for incorrect module name

If the author component of a module name is omitted, the puppet module install <author-module> command provides a name suggestion in the error message. PUP-10641

Puppet reports the license gem on Apache

Puppet now reports the Apache 2.0 license when installed as a gem. PUP-11118

Support for Debian 11 Bullseye amd64

This release adds support for Debian 11 Bullseye amd64. PUP-11030

macOS puppet-agent code-signs executables

The macOS puppet-agent AIO packages now provide code-signed executables for puppet and pxp-agent. PA-3756

Solaris OpenSSL patching replaced with compiler arguments

This release adds AES CTR-DRGB performance improvements to Puppet’s vendored OpenSSL. PA-3698

The empty function accepts Sensitive data types

The empty function now accepts Sensitive data types, which allows you to test a Sensitive variable that is neither nil or empty. For example, a variable in an ERB template. Contributed by Puppet community member cocker-cc. PUP-11124

The unwrap function accepts Any data type

The unwrap function now accepts the Any data type. This means that the component modules, such as puppetlabs-postgresql, can migrate to using Sensitive values, while still accepting non-Sensitive values. You do not need to special case when unwrapping the value. Contributed by Puppet community member cocker-cc. PUP-11123

The exec provider supports commands as an Array

When a command is an Array of Strings, passed as [cmdname, arg1, ...], it is now executed directly instead of being passed to the standard shell. This is supported for the following exec parameters: comand, onlyif, unless, refresh. Note that onlyif and unless already accept multiple commands as an Array — you need to pass the value as an Array of Array to use this new behaviour. PUP-5704

Embedded Ruby (ERB) templates allow a leading Byte Order Mark (BOM)

Previously, when a template contained a BOM, it was preserved by the template function and included in the resulting file or PowerShell command. Puppet now passes the bom option when reading the file, removing the BOM as it is read. PUP-8243

Resolved issues

Puppet Module Tool (PMT) does not install a module when module_working_dir contains backslashes

This release fixes an issue that prevented the puppet module install command working on Windows when module_working_dir contained backslashes, for example, C:\modules. PUP-4884

Node resource names are overlapping with other resources

Previously, if a node statement had the same name as the included class, Puppet ignored the class, as it thought it had already been included. This issue is now fixed. PUP-3995

Puppet fails if the setting value is numbers

Puppet settings can now contain all numbers, for example, certname=000000000180. PUP-7785

The Puppet user type does not honor purge_ssh_keys: false

Puppet no longer emits a warning if the purge_ssh_keys parameter for the user type is set to false (the default) and the sshkeys_core module is not installed. PUP-11131

The --extra cli option is not functional

The puppet help command no longer displays the --extra command line option. PUP-8700

The parsedfile provider produces an undefined method each for nil:NilClass

Puppet now prints an error if a parsedfile provider returns nil, for example, when using the nagios_core module. PUP-9369

Unclear error message if user or group providers are not suitable

Puppet now prints a more detailed error message if the user or group providers are not functional. PUP-9825

The Puppet::Resources.search method fails when conditions are provided

This release fixes an issue that prevented the Puppet::Resource.indirection.search method from accepting conditions when filtering results. PUP-7799

Repository error message URL is missing part of the path

Previously, the puppet module command reported an incorrect URL in the error message when the module_repository setting was overridden. This is now fixed. PUP-8650

The desired_value file mode is reported without leading zeros

Puppet now reports file modes with a leading zero in the desired_value field ⁠— for example, 0755 ⁠— which is consistent with the previous_value. PUP-7493

Filebucket fails when using a non-default environment from the server

The filebucket application no longer requires an environment to exist locally. PUP-10796

Unable to load PKey.read with private keys

Puppet agent now loads private keys in the PKCS#8 format. PUP-11082

Cached environments are not deleted when the directory is removed

Puppet now removes environments that are no longer on disk. PUP-11129

Unable to run the puppet resource command when the environment is specified

Previously, running puppet resource on the agent with an invalid environment would fail. With this release, the application falls back to the default environment, if the specified one does not exist. PUP-6554

Puppet prints unnecessary errors in debug

Puppet no longer prints an unnecessary error message when resolving account names to security identifiers on Windows. PUP-10967

Setting age=0 on a tidy resource does not remove all files

Previously, the age parameter of the tidy resource only removed files older than those specified. This is now fixed and Puppet removes all files. PUP-11079

The agent_specified_environment fact is not populating

This release fixes an issue where the agent_specified_environment fact did not populate when the environment was set in the [agent] section. This is now fixed and populates in the following order: CLI, agent section, main section. PUP-6801

pip ensure=>latest fails with pip>=20.3.0

In version 20.3b1, pip removed the ability to list available versions of a package. This release adds the --use-deprecated=legacy-resolver argument so that you can query available versions. PUP-11029

The pxp-agent does not use the wrapper script

The pxp-agent service script on the AIX, OSX, and Solaris platforms now manipulates the service using the wrapper script located in /opt/puppetlabs/bin/pxp-agent, which cleans up the linker environment before calling the actual environment. This prevent failures due to incompatible libraries being loaded. To modify the pxp-agent linker environment, directly call the pxp-agent binary, for example, /opt/puppetlabs/puppet/bin/pxp-agent. PCP-890

Puppet 7.8.0

Released June 2021.

Enhancements

Support for Ruby 3

Puppet adds experimental support for Ruby 3 and is now tested in CI. PUP-11076

Improve enable=delayed_start error message

This release improves an error message to properly convey that you cannot set a systemd service to delayed_start on operating systems other than Windows. PUP-11062

Ruby support long paths on Windows

This release adds the following patch into the Puppet Agent vendored Ruby. The patch implements long path support on Windows. PA-3759

Bump semantic_puppet version to 1.0.4

This release bumps semantic_puppet to version 1.0.4 in order to support Ruby 3. PA-3827

Bump curl to 7.77.0

This release bumps the curl dependency to 7.77.0. PA-3762

Support for Fedora 34 FOSS

This release adds support for Fedora 34 (64-bit package) FOSS. PA-3600

Resolved issues

NIM provider used very restrictive regular expressions

Previously, the NIM provider only allowed numbers when parsing RPM release tags and didn't accept bff (installp) packages marked as security updates in the header. In this release, Puppet allows installation of such packages. PUP-3631

Sensitive instances shared the same value yet weren’t equal

Previously, two type Sensitive instances failed to compare as equal—despite sharing the same underlying strings. In this release, comparisons such as $a = Sensitive("secret"); $b = Sensitive("secret"); notice($a == $b) now return as true. PUP-11061

User keychains were inaccessible to Puppet Agent

Previously, user keychains were inaccessible to Puppet Agent if you ran Puppet Agent through the macOS daemon. This bug is now fixed. PUP-11081

SemVer datatype components failed to pass as hash or argument list

Previously, the build or prerelease components of the SemVer datatype failed to pass as a hash or list of arguments. This bug is now fixed. PUP-11077

Nil vertices caused resource management errors

Previously, managing resources that call the generate method — failed when using the puppet resource subcommand— due to the presence of a nil vertex in the catalog. To fix this bug, Puppet can no longer add nil vertices to the catalog. PUP-11074

Puppet returned an error when specifying the purge_ssh_keys parameter

Previously, Puppet returned an error if you specified the purge_ssh_keys parameter for a user resource that didn’t previously exist. To fix this bug, Puppet prioritizes the ensure property of a user before the purge_ssh_keys parameter. PUP-11067

Puppet cannot change/set new user passwords on macOS Big Sur

Previously, you could not set or change the password of a new user created on macOS Big Sur. This bug is now fixed by ensuring the ApplicationAuthority field exists whenever you create a new user. PUP-11026

Puppet returned an error when creating new users on macOS 10.14

Previously, if you created a new user on macOS 10.14, Puppet returned an Operation not permitted @ rb_sysopen error. This bug is now fixed.PUP-11095

Masking service failed

Previously, Puppet failed to mask a systemd service that did not exist. This bug is now fixed. PUP-10974

Puppet 7.7.0

Released June 2021.

We would like to thank the following Puppet community members for their contributions to this release: tobias-urdin and nmaludy.

Enhancements

Puppet loads internal files using the require_relative method

When loading internal files, Puppet now uses the require_relative method, eliminating thousands of file system calls. This accounts for between 5 to 15% of the total number of file system calls for different platforms. PUP-11055

Case sensitive parameter for the fqdn_rand() function

The fqdn_rand() function now accepts an optional parameter to downcase the FQDN fact, so that the function's result is not case sensitive. You must pass the parameter after the seed string, for example, fqdn_rand(100, 'expensive job 1', true). By default, the function remains case-sensitive. PUP-10922

File limit with the max_files parameter

By default, the file and tidy resource types generate a warning on the Puppet Enterprise (PE) console and report when Puppet tries to manage more than 1000 files with the recurse parameter set to true. The file and tidy resource types now support a new parameter — max_files — that enforces a hard limit. If the number of recursive files is greater than the limit, the agent run fails. You can set the max_files parameter to -1 to disable the warning. PUP-10946

Improved Ruby performance

This release improves the performance of Ruby, resulting in the follow changes:

  • Puppet now loads and runs faster — particularly on Windows. PA-3732
  • New Ruby performance patches — reducing 50-90% of file IO when loading Puppet and Facter. PA-3732

Support for macOS 11 and Red Hat 8 Power

This release adds support for macOS 11 Big Sur (64-bit packages only) and Red Hat 8 on IBM Power. PA-3529, PA-3612.

Resolved issues

Ruby 3 freezes CHILD_STATUS and cannot be stubbed

This release eliminates the usage of the $CHILD_STATUS global variable in the built-in service and package providers. PUP-11048

Ruby 3 removed URI.escape/unescape

This release eliminates calls to URI.escape/unescape, which was deprecated in Ruby 2.x and removed in Ruby 3. PUP-11046

Agent failures with server_list

Previously, when Puppet processed server_list and tried to find a functional server, it threw an error if it could not connect, causing the agent to fail. This is now fixed. PUP-10844

Puppet does not specify SELinux filetype when getting the default context

Previously, Puppet created files with the wrong default SELinux context, which was only corrected after a subsequent Puppet run. This is now fixed. Contributed by Puppet community member tobias-urdin. PUP-7559

Unable to mask a static systemd service

This release fixes an issue where the systemd provider did not mask static systemd services. Contributed by Puppet community member nmaludy. PUP-11034

Unable to update UserRightAssignment

Previously, validating the logonaccount and logonpassword parameters for the service resource on Windows failed too early. This release moves the parameters further down the catalog compilation order list to avoid early errors. PUP-10999

PUPPET_SERVER MSI install property does not work

Previously, using PUPPET_SERVER as an MSI property did not set the server setting. This is now fixed. PA-3667

Puppet 7.6.1

Released April 2021.

We would like to thank the following Puppet community members for their contributions to this release: gcampbell12.

Enhancements

Puppet module type scripts directory

This release adds a new subdirectory to the scripts/ module class. It automatically generates the functions in the class and retrieves the available scripts. This helps to standardize specific file loading from either the files directory or scripts directory. PUP-10996

Backport logic to detect migrated CA directory location

After migrating the CA directory, Puppet now reports the correct cadir setting value. PUP-11004

Curl bumped to 7.76.0

This release bumps Curl to 7.76.0, fixing the following CVEs:

PA-3690

Ruby bumped to 2.7.3

This release bumps Ruby to 2.7.3, fixing the following CVEs:

PA-3696

Resolved issues

Race condition with agent_disabled_lockfile

This release fixes a race condition that caused the agent to become disabled and no longer enforce desired state. Contributed by Puppet community member gcampbell12. PUP-11000

User resource with forcelocal and groups attributes set fails if /etc/group contains empty lines

This release fixes an issue where Puppet failed when applying user resources with forcelocal if there were empty lines in /etc/group. PUP-10997

Unable to install gems with the puppet_gem provider on Windows

Previously, if you used Puppet as a library, environment.bat was not sourced and led to an unset PUPPET_DIR. As puppet_gem relied on this to build the gem.bat path, it used a non-existing path, making this provider unsuitable. This release updates the puppet_gem provider to use Gem.default_bindir, which determines the location of the executables. To avoid accidental usage of the puppet_gem provider with system Ruby, we have also added a confine to the aio_agent_version fact. PUP-10964

Changing a Puppet setting in a catalog invalidates the environment cache in multithreaded mode

You can now change the value of Puppet's rich_data setting at runtime, without it invalidating the environment cache. PUP-10952

Puppet cannot parse systemd instances when list-unit-files output has an additional column

This release fixes an issue affecting the parsing of systemd service instances caused by a change in the systemctl list-unit-files command output. PUP-10949

Cannot ensure dnfmodule with no default profile

Previously, using the dnfmodule provider to install a module with no default profile — without passing the enable_only parameter — failed with newer versions of DNF. PUP-11024

Puppet 7.5.0

Released March 2021.

New features

The puppet ssl show command

The puppet ssl show command prints the full-text version of a host's certificate, including extensions. PUP-10888

The ciphers setting

The ciphers setting configures which TLS ciphersuites the agent supports. The default set of ciphersuites is the same, but you can now make the list of ciphersuites more restricted, for example, to only accept TLS v1.2 or greater ciphersuites. PUP-10889

The GlobalSignRoot CA R3

This release adds the GlobalSignRoot CA R3 certificate for rubygems.org. PA-3525

Resolved issues

The splat operator in a virtual query is not supported

This release fixes a regression in Puppet 7.x that prevented the splat operator from being used to override resource attributes in a resource collector. PUP-10951

Windows package provider continues to read DisplayVersion key after it is embedded NULL

Previously, Puppet would not stop reading the registry at the correct WCHAR_NULL because it was encoded to UTF-16LE, causing Puppet to read bad data and fail. This is now fixed. PUP-10943

Listing environments during code deploys prevents environment cache invalidation

Previously, catalog compilations for a newly created environment directory could fail if the environment was listed while the directory was being created. This issue only occurred when using an environment_timeout value greater than 0 and less than unlimited. This is now fixed. PUP-10942

Syntax error in previously valid Puppet code due to removal of keywords

The application, consumes, produces and site application orchestration keywords were previously removed from the reserved keywords list, causing syntax errors in Puppet code. This is now fixed. PUP-10929

Retrieve SID for users under APPLICATION PACKAGE AUTHORITY

A known issue with LookupAccountNameW caused Puppet to fail when managing Windows users under APPLICATION PACKAGE AUTHORITY with fully qualified names. This is now fixed and an account name sanitization step has been added to prevent faulty queries. PUP-10899

Retrieving the current user with the fully-qualified username fails on Windows

Previously, retrieving the current username SID on Windows caused Puppet to fail in certain scenarios, for example, when the user was a secondary domain controller. This release adds a fallback mechanism that uses the fully qualified domain name for lookup. PUP-10898

Puppet 7.4.1

Released February 2021.

Resolved issues

Puppet users with forcelocal are no longer idempotent

This release fixes a regression where setting the gid parameter on a user resource with forcelocal was not idempotent. PUP-10896

Puppet 7.4.0

Released February 2021.

New features

New --timing option in puppet facts show

This release adds a --timing option in the puppet facts show command. This flag shows you how much time it takes to resolve each fact. PUP-10858

Resolved issues

User resource with forcelocal uses getent for groups

The useradd provider now checks the forcelocal parameter and gets local information on the groups (from /etc/groups) and gid (from etc/passwd) of the user when requested. PUP-10857

Slow Puppet agent run after upgrade to version 6

This release improves the performance of the apt package provider when removing packages by reducing the calls to apt-mark showmanual. PUP-10856

The apt provider does not work with local packages

The apt package provider now allows you to install packages from a local file using source parameter. PUP-10854

The puppet facts show --value-only command displays a quoted value

Previously, the puppet facts show --value-only <fact> command emitted the value as a JSON string, which included quotes around the value, such as {{"RedHat"}}. It now only emits the value. PUP-10861

Puppet 7.3.0

Released January 2021.

New features

The serverport setting

The serverport setting is an alias for masterport. PUP-10725

Enhancements

Multiple logdest locations in puppet.conf accepted

You can set multiple logdest locations using a comma separated list. For example: /path/file1,console,/path/file2. PUP-10795

The puppet module install command lists unsatisfiable dependencies

If the puppet module install command fails, Puppet returns a more detailed error, including the unsatisfiable module(s) and its ranges. PUP-9176

New --no-legacy option to disable legacy facts

By default, puppet facts show displays all facts, including legacy facts. This release adds a --no-legacy option to disable legacy facts when querying all facts. PUP-10850

Resolved issues

The puppet apply command creates warnings

This release eliminates Ruby 2.7.x warnings when running puppet apply with node statements. PUP-10845

Remove Pathname#cleanpath workaround

This release removes an unnecessary workaround when cleaning file paths, as Ruby 1.9 is no longer supported. PUP-10840

The allow * error message shown during PE upgrade

Puppet no longer prints an error if fileserver.conf contains allow * rules. It continues to print an error for all other rules, as Puppet's legacy authorization is no longer supported and is superseded by Puppetserver's authorization. PUP-10851

3x functions cannot be called from deferred functions in Puppet agent

This release allows deferred 3.x functions, like sprintf, to be called during a Puppet agent run. PUP-10819

Cached catalog contains the result of deferred evaluation instead of the deferred function

Puppet 6.12.0 introduced a regression that caused the result of a deferred function to be stored in the cached catalog. As a result, an agent running with a cached catalog would not re-evaluate the deferred function. This is now fixed. PUP-10818

puppet facts show fact output differs from facter fact

The output format is different between Facter and Puppet facts when a query for a single fact is provided. This is now fixed. PUP-10847

Issue with Puppet creating production folder when multiple environment paths are set

Previously, the production environment folder was automatically created at every Puppet ran in the first search path, if it did not already exist. This release ensures Puppet searches all the given paths before creating a new production environment folder. PUP-10842

Puppet 7.2.0

This version of Puppet was never released.

Puppet 7.1.0

Released December 2020.

Enhancements

Reduced query time for system user groups

The time it takes to query groups of a system user has been reduced on Linux operating systems with FFI. The getgrouplist method is also available. PUP-10774

Log rotation for Windows based platforms

You can now configure the pxp-agent to use the Windows Event Log service by setting thelogfile value to eventlog. PA-3492

Log rotation for macOS based platforms

This release enables log rotation for the pxp-agent on OSX platforms. PA-3491

Added server alias for routes.yaml

When routes.yaml is parsed, it accepts either server or master applications. PUP-10773

OpenSSL bumped to 1.1.1i

This release bumps OpenSSL to 1.1.1i. PA-3513

Curl bumped to 7.74.0

This release bumps Curl to 7.74.0. PA-3512

Resolved issues

The Puppet 7 gem is missing runtime dependency on scanf

This is fixed and you can now run module tests against the Puppet gem on Ruby 2.7. PUP-10797

The puppet node clean action LoggerIO needs to implement warn

In Puppet 7.0.0, the puppet node clean action failed if you had cadir in the legacy location or inside the ssldir. This was a regression and is now fixed. PUP-10786

Calling scope#tags results in undefined method

Previously, calling the tags method within an ERB template resulted in a confusing error message. The error message now makes it clear that this method is not supported. PUP-10779

User resource is not idempotent on AIX

The AIX user resource now allows for password lines with arbitrary whitespace in the passwd file. PUP-10778

Fine grained environment timeout issues

Previously, if the environment.conf for an environment was updated and the environment was cleared, puppetserver used old values for per-environment settings. This happened if the environment timed out or if the environment was explicitly cleared using puppetserver's environment cache REST API. With this fix, if an environment is cleared, Puppet reloads the per-environment settings from the updated environment.conf. PUP-10713

FIPS compliant nodes are returning an error

This release fixes an issue on Windows FIPS where Leatherman libraries loaded at the predefined address of the OpenSSL library. This caused the OpenSSL library to relocate to a different address, failing the FIPS validation. This is fixed and leatherman compiled with dynamicbase is disabled on Windows. PA-3474

User provider with uid/gid as Integer raises warning

This release fixes a warning introduced in Ruby 2.7 that checked invalid objects (such as Integer) against a regular expression. PUP-10790

Puppet 7.0.0

Released November 2020.

New features

The puppet facts show command

You can use the puppet facts show command to retrieve a list of facts. By default, it does not return legacy facts, but you can enable it to with the --show legacy option. This command replaces puppet facts find as the default Puppet facts action. PUP-10644 and PUP-10715

JSON terminus for node and report

This release implements JSON termini for node and report indirection. The format of the last_run_report.yaml report can be affected by the cache setting key of the report terminus in the routes.yaml file. To ensure the file extension matches the content, update the lastrunreport configuration to reflect the terminus changes (lastrunreport = $statedir/last_run_report.json). PUP-10712

JSON terminus for facts

This release adds a new JSON terminus for facts, allowing them to be stored and loaded as JSON. Puppet agents continue to default to YAML, but you can use JSON by configuring the agent application in routes.yaml. Puppet Server 7 also caches facts as JSON instead of YAML by default. You can re-enable the old YAML terminus in routes.yaml. PUP-10656

Public folder (default location for last_run_summary.yaml)

There is a new folder with 0755 access rights named public, which is now the default location for the last_run_summary.yaml report. It has 640 file permissions. This makes it possible for a non-privileged process to read the file. To relax permissions on the last run summary, set the group permission on the file in puppet.conf to the following: lastrunsummary = $publicdir/last_run_summary.yaml { owner = root, group = monitoring, mode = 0640 }. Note that if you use tools that expect to find last_run_summary.yaml in vardir instead of publicdir, you might experience breaking changes.PUP-10627

The settings_catalog setting

To load Puppet more quickly, you can set the settings_catalog setting to false to skip applying the settings catalog. The setting defaults to true. PUP-8682

New numeric and port setting types

This release adds a new port setting type, which turns the given value to an integer, and validates it if the value is in the range of 0-65535. Puppet port can use this setting type. PUP-10711

MSI PUPPET_SERVER and alias

This release adds a new Windows Installer property called PUPPET_SERVER. You can use this as an alias to the existing PUPPET_MASTER_SERVER property. PA-3440

New GPG signing key

Puppet has a new GPG signing key. See verify packages for the new key.

Enhancements

Ruby version bumped to 2.7

The default version of Ruby is now 2.7. The minimum Ruby version required to run Puppet 7 is now 2.5. After upgrading to Puppet 7, you may need to use the puppet_gem provider to ensure all your gems are installed. PUP-10625

Default digest algorithm changed to sha256

Puppet 7 now uses sha256 as the default digest algorithm. PUP-10583

Gem provider installs gems in Ruby

The gem provider now installs gems in Ruby by default. Use the puppet_gem provider to reinstall gems in the Ruby distribution vendored in Puppet. For example, if custom providers or deferred functions require gems during catalog application. PUP-10677

FFI functions, structs and constants moved to a separate Windows module

To increase speed, we have moved FFI functions, constants and structures out of Puppet::Util::Windows. PUP-10606

Default value of ignore_plugin_errors changed from true to false

The default value for ignore_plugin_errors is now false. This stops Puppet agents failing to pluginsync. PUP-10598

Interpolation of sensitive values in EPP templates

Previously, if you interpolated a sensitive value in a template, you were required to unwrap the sensitive value and rewrap the result. Now the epp and inline_epp functions automatically return a Sensitive value if any interpolated variables are sensitive. For example: inline_epp("Password is <%= Sensitive('opensesame') %>" ). Note that these changes just apply to EPP templates, not ERB templates. PUP-8969

shkeys_core module bumped to 2.2.0

Puppet 7 bumps the sshkeys_core modules to 2.2.0 in the Puppet agent. The default namevar for keys now includes the encryption type in addition to the hostname. PA-3473

Call simple server status endpoint

Puppet updates the endpoint for checking the server status to /status/v1/simple/server. If the call returns a 404, it makes a new call to /status/v1/simple/master, and ensures backwards compatibility. PUP-10673

Default value of disable_i18n changed from false to true

The default value for the disable_i18n setting has changed from false to true and locales are not pluginsynced when i18n is disabled. PUP-10610

Pathspec no longer vendored

The pathspec Ruby library is no longer vendored in Puppet. If you require this functionality, you need to install the pathspec Ruby gem. PUP-10107

Deprecations and removals

func3x_check setting removed

The func3x_check setting has been removed. PUP-10724

master_used report parameter removed

The deprecated master_used parameter has been removed. Instead use server_used. PUP-10714

facterng feature flag removed

The facterng feature flag has been removed. It is not needed anymore as Puppet 7 uses Facter 4 by default. PUP-10605

held removed from apt provider

The apt provider no longer accepts deprecated ensure=held. Use the mark attribute instead. PUP-10597

Method from DirectoryService removed

The deprecated DirectoryService#write_to_file method has been removed. PUP-10489

Method from Puppet::Provider::NameService removed

The deprecated Puppet::Provider::NameService#listbyname method has been removed. PUP-10488

Methods from TypeCalculator removed

The deprecated TypeCalculator.enumerable has been removed, and the functionality has been moved to Iterable. PUP-10487

Enumeration type removed

The deprecated Enumeration class has been removed, and its functionality has been moved to Iterable. PUP-10486

Puppet::Util::Yaml.load_file removed

The deprecated Puppet::Util::Yaml.load_file method has been removed. PUP-10475

Puppet::Resource methods removed

The following deprecated Puppet::Resource methods have been removed:

  • Puppet::Resource.set_default_parameters
  • Puppet::Resource.validate_complete
  • Puppet::Resource::Type.assign_parameter_values. PUP-10474

legacy auth.conf support removed

The legacy auth.conf has been deprecated for several major releases. Puppet 7 removes all support for legacy auth.conf. Instead, authorization to Puppet REST APIs is controlled by puppetserver auth.conf. In addition, the allow and deny rules in fileserver.conf are now ignored and Puppet logs an error for each entry. The rest_authconfig setting has also been removed. PUP-10473

Puppet.define_settings removed

The deprecated Puppet.define_settings method has been removed. PUP-10472

Application orchestration language features removed

The deprecated application orchestration language features have been removed. The keywords application, site, consumes and produces, and the export and consume metaparameters, now raise errors. The keywords are still reserved, but can’t be used as a custom resource type or attribute name. The environment catalog REST API has also been removed, along with supporting classes, such as the environment compiler and validators. PUP-10446

Puppet::Network::HTTP::ConnectionAdapter removed

The Puppet::Network::HTTP::ConnectionAdapter has been removed, and contains the following breaking changes:

  • The Client networking code has been moved to Puppet::HTTP.
  • The Puppet::Network::HttpPool.http_instance method has been removed.
  • The Puppet.lookup(:http_pool) has been removed.
  • The deprecated Puppet::Network::HttpPool.http_instance and connection methods have been preserved. PUP-10439

environment_timeout_mode setting removed

The environment_timeout_mode setting has been removed. Puppet no longer supports environment timeouts based on when the environment was created. In Puppet 7, the environment_timeout setting is always interpreted as 0 (never cache), unlimited (always cache), or from when the environment was last used. PUP-10619

Networking code from the parent REST terminus removed

The Networking code from the parent REST terminus has been removed, and is a breaking change for any REST terminus that relies on the parent REST terminus to perform the network request and process the response. The REST termini must implement the find, search, save and destroy methods for their indirected model. PUP-10440

Dependency on http-client gem removed

The dependency on the http-client gem has been removed. If you have a Puppet provider that relies on this gem, you must install it. PUP-10490

HTTP file content terminus removed

The HTTP file content terminus has been removed. It is no longer possible to retrieve HTTP file content using the indirector. Instead, use Puppet's builtin HTTP client instead: response = Puppet.runtime[:http].get(URI("http://example.com/path")). PUP-10442

Puppet::Util::HttpProxy.request_with_redirects removed

The Puppet::Util::HttpProxy.request_with_redirects method has been removed, and moves the Puppet::Util::HttpProxy class to Puppet::HTTP::Proxy. The old constant is backwards compatible. PUP-10441

Puppet::Rest removed

Puppet::Rest removed and Puppet::Network::HTTP::Compression have been removed. This change moves Puppet::Network::Resolver to Puppet::HTTP::DNS and deprecates Puppet::Network::HttpPool methods. PUP-10438

Remove strict_hostname_checking removed

The deprecated strict_hostname_checking and node_name settings have been removed. The functionality of these settings is possible using explicit constructs within a site.pp or fully featured enc. PUP-10436

puppet module build, generate and search actions removed

The puppet module build, generate and search actions have been removed. Use Puppet Development Kit (PDK) instead.PUP-10387

puppet status application has been removed

The deprecated puppet status application has been removed. PUP-10386

The puppet cert and key commands removed

The non-functioning puppet cert and puppet key commands have been removed. Instead use puppet ssl on the agent node and puppetserver ca on the CA server. PUP-10369

SSL code, termini and settings removed

The following SSL code, termini and settings have been removed:

  • Puppet::SSL::Host

  • Puppet::SSL::Key

  • Puppet::SSL::{Certificate,CertificateRequest}.indirection

  • Puppet::SSL::Validator*

  • ssl_client_ca_auth

  • ssl_server_ca_auth PUP-10252

The func3x_check setting has been removed

The setting to turn off func 3x API validation has been removed. Now all 3x functions are validated. PUP-9469

The future_features logic has been removed

The unused future_features setting has been removed. PUP-9426

The puppet man application has been removed

The puppet man application is no longer needed and has been removed. The agent package now installs man pages so that man puppet produces useful results. Puppet's help system (puppet help) is also available. PUP-8446

The execfail method from util/execution has been removed

The following deprecated methods have been removed:

  • Puppet::Provider#execfail
  • Puppet::Util::Execution.execfail. PUP-7584

The win32-process has been removed

The Puppet dependency on the win32-process gem has been removed. You can implement the functionality using FFI. PUP-7445

The win32-service gem has been removed

The dependency on the win32-service gem has been removed and uses the Daemon class in Puppet instead. PUP-5758

The win32-security gem has been removed from Puppet

To improve Puppet's handling of Unicode user and group names on Windows, some of the code interacting with the Windows API has been rewritten to ensure wide character (UTF-16LE) API variants are called. As a result, Puppet no longer needs the win32-security gem. Any code based references to the gem have been removed. The gem currently remains for backward compatibility, but is to be removed in a future release. PUP-5735

The capability to install an agent on Windows 2008 and 2008 R2 has been removed

You can no longer install Puppet 7 agents on Windows versions lower than 2012. PA-3364

Support for Ruby versions older than 2.5 removed

Support for Ruby versions older than 2.5 has been removed, and Fixnum and Bignum have been replaced with Integer. PUP-10509

dir monkey-patch removed

This external dependency on the win32/dir gem has been removed and replaces CSIDL constants with environment variables. PUP-10653

Master removed from docs

Documentation for this release replaces the term master with primary server. This change is part of a company-wide effort to remove harmful terminology from our products. For the immediate future, you’ll continue to encounter master within the product, for example in parameters, commands, and preconfigured node groups. Where documentation references these codified product elements, we’ve left the term as-is. As a result of this update, if you’ve bookmarked or linked to specific sections of a docs page that include master in the URL, you’ll need to update your link.

Resolved issues

Puppet agent installation fails when msgpack is enabled on puppetserver

Previously, the agent failed to deserialize the catalog and fail the run if the msgpack gem was enabled but not installed. Now the agent only supports that format when the msgpack gem is installed in the agents vendored Ruby. PUP-10772

Puppet feature detection leaves Ruby gems in a bad state

This release fixes a Ruby gem caching issue that prevented the agent from applying a catalog if a gem was managed using the native package manager, such as yum or apt. PUP-10719

Puppet 6 agents do not honor the usecacheonfailure setting when using server_list

Previously, when server_list was used when there was no server accessible, the Puppet run failed even if usecacheonfailure was set to true. Now Puppet only fails if usecacheonfailure is set to false. PUP-10648

Setting certname in multiple sections bypasses validation

Previously, Puppet only validated the certname setting when specified in the main setting, but not if the value was in a non-global setting like agent. As a result, it was possible to set the certname setting to a value containing uppercase letters and prevent the agent from obtaining a certificate the next time it ran. Puppet now validates the certname setting regardless of which setting the value is specified in. PUP-9481

Issues caused by backup to the local filebucket

By default, Puppet won’t backup files it overwrites or deletes to the local filebucket, due to issues where it became unbounded. You can re-enable the local filebucket by setting File { backup => 'puppet' } as a resource default. PUP-9407

Remove future feature flag for prefetch_failed_providers in transaction.rb

If a provider prefetch method raises a LoadError or StandardError, the resources associated with the provider are marked as failed, but unrelated resources are applied. Previously this behavior was controlled by the future_features flag, and disabled by default. PUP-9405

Change default value of hostcsr setting

The default value of the hostcsr setting has been updated to match where Puppet stores the certificate request (CSR) when waiting for the CA to issue a certificate. PUP-9346

Refactor the SMF provider to implement enableable semantics

Previously, the SMF provider did not properly implement enableable semantics. Now enable and ensure are independent operations where enable handles whether a service starts or stops at boot time, and ensure handles whether a service starts or stops in the current running instance. PUP-9051

The list of reserved type names known to the parser validator is incomplete

A class or defined type in top scope can no longer be named init, object, sensitive, semver, semverrange, string, timestamp, timespan or typeset . You can continue to use these names in other scopes such as mymodule::object. PUP-7843

Export or virtualize class error

Previously, Puppet returned a warning or error if it encountered a virtual class or an exported class, but it still included resources from the virtual class in the catalog. Now Puppet always error on virtual and exported classes. PUP-7582

Puppet::Util::Windows::String.wide_string embeds a NULL char

This release removes a Ruby workaround for wide character strings on Windows. PUP-3970

puppet config set certname accepts upper-case names

Previously, the puppet config set command could set a value that was invalid, causing Puppet to fail the next time it ran or the service was restarted. Now the command validates the value before committing the change to puppet.conf. PUP-2173

Unable to read last_run_summary.yaml from user

Puppet agent code now aligns with the new last_run_summary.yaml location. PA-3253

Puppet known issues

These are the known issues in Puppet V7.

Package collection on MacOS triggers attempt to install developer tools for Python

When running Puppet 7.8.0 on macOS, Puppet may attempt to collect Python packages, which are no longer used in macOS. An error message states that PIP packages cannot be collected, with a prompt to install associated command-line developer tools. This behavior is triggered by a stub executable present in macOS. PUP-11508

User and group management on macOS 11 and later requires Full Disk Access (FDA)

To manage users and groups with Puppet on macOS 11 and later, you must grant Puppet Full Disk Access (FDA). You must also grant FDA to the parent process that triggers your Puppet run. For example:
  • To run Puppet in a server-agent infrastructure, you must grant FDA to the pxp-agent.

  • To run Puppet from a remote machine with SSH commands, you must grant FDA to sshd.

  • To run Puppet commands from the terminal, you must grant FDA to terminal.app.

To give Puppet access, go to System Preferences > Security & Privacy > Privacy > Full Disk Access, and add the path to the Puppet executable, along with any other parent processes you use to run. For detailed steps, see Add full disk access for Puppet on macOS 10.14 and newer. Alternatively, set up automatic access using Privacy Preferences Control Profiles and a Mobile Device Management Server. PA-2226, PA-2227

Hiera knockout_prefix is ineffective in hierarchies more than three levels deep

When specifying a deep merge behaviour in Hiera, the knockout_prefix identifier is effective only against values in an adjacent array, and not in hierarchies more than three levels deep. HI-223

Specify the epoch when using version ranges with the yum package provider

When using version ranges with the yum package provider, there is a limitation which requires you to specify the epoch as part of the version in the range, otherwise it uses the implicit epoch `0`. For more information, see the RPM packaging guide. PUP-10298

Deferred functions can only use built-in Puppet types

Deferred functions can only use types that are built into Puppet (for example String). They cannot use types from modules like stdlib because Puppet does not plugin-sync these types to the agent. PUP-8600

The Puppet agent installer fails when systemd is not present on Debian 10 and earlier

The puppet-agent package does not include sysv init scripts for Debian 10 (buster) or later. If you disabled or removed systemd, puppet-agent installation and Puppet agent runs can fail.

Puppet Server release notes

Puppet Server 7.17.4

Released February 2025 and shipped with Puppet 7.35.0.

This release was necessary to accommodate dependency updates. No new features or fixes are introduced.

Puppet Server 7.17.3

Released October 2024 and shipped with Puppet 7.34.0.

This release adds support for Debian 12 "Bookworm" amd64. In addition, the puppet-profiler PuppetDB metrics have been enhanced and expanded.

Enhancements

Debian 12 "Bookworm" amd64 support. Puppet Server now supports Debian 12 "Bookworm" amd64. Native packages are available at https://apt.puppet.com.

Improved and expanded PuppetDB metrics. The puppet-profiler PuppetDB metrics returned via the status API endpoint at debug level have been refactored to improve performance, and to resolve a potential issue when running on Java 11. The following new metrics have also been added:

  • reports.process

  • catalog.save

  • facts.save

  • facts.find

  • facts.search

  • payload.format

Puppet Server 7.17.2

Released July 2024 and shipped with Puppet 7.32.1.

This release was necessary to accommodate dependency updates. No new features or fixes are introduced.

Puppet Server 7.17.1

Released June 2024 and shipped with Puppet 7.31.0.

JRuby updated to resolve minor defects. The JRuby implementation is updated from 9.3.9.0 to 9.3.14.0. The update resolves several minor issues but does not change the functionality of Puppet Server.

Puppet Server 7.17.0

Released April 2024 and shipped with Puppet 7.30.0.

No release notes.

Puppet Server 7.16.0

Released February 2024 and shipped with Puppet 7.29.0.

Improved schema validation logging.

Puppet Server 7.15.0

Released January 2024 and shipped with Puppet 7.28.0.

Only send compiler header for v3 catalog requests. PUP-11973

Rubygems. Updated rubygems shipped with Puppet Server to fix memory leak.

CONFDIR variable. Fixed dropsonde configuration option CONFDIR env variable. SERVER-3263

Puppet Server 7.14.0

Released November 2023 and shipped with Puppet 7.27.0.

No release notes.

Puppet Server 7.13.0

Released August 2023 and shipped with Puppet 7.26.0.

Operating system support. Added support for RHEL 9 and Ubuntu 22.04.

Puppet Server 7.12.0

Released June 2023 and shipped with Puppet 7.25.0.

No release notes.

Puppet Server 7.11.0

Released April 2023 and shipped with Puppet 7.24.0.

Enhancements

Update Puppet Server CA CLI gem to 2.5.0. The included Puppet Server CA CLI gem, which adds the ability to remove expired or arbitrary certs using the prune action, and the ability to remove expired, arbitrary, or all certs from the signed directory using the delete action.

Resolved issues

Puppet Server dependency update improvements. Updating Puppet Server dependencies now provides better errors when given config files with invalid extensions, no longer crashes in rare cases when receiving SIGHUP, and warns in the log file when unable to check for updates.

Puppet Server 7.10.0

This version was never released.

Puppet Server 7.9.5

Released February 2023 and shipped with Puppet 7.23.0.

No release notes.

Puppet Server 7.9.4

This version was never released.

Puppet Server 7.9.3

Released December 2022 and shipped with Puppet 7.21.0.

No release notes.

Puppet Server 7.9.2

Released October 2022 and shipped with Puppet 7.20.0.

No release notes.

Puppet Server 7.9.0

Released August 2022 and shipped with Puppet 7.18.0.

Resolved issues

Upgrade JRuby to 9.3.4.0. Puppet Server now uses JRuby 9.3.4.0. SERVER-3133

Puppet Server 7.8.0

Released May 2022 and shipped with Puppet 7.17.0.

Enhancements

Make Puppet Server http client respect include_system_store option. Puppet Server's Ruby HTTP client now supports loading certificates from the system trust store that is included with Puppet Agent, as well as loading certs from a file or Java cert store at an arbitrary location via the ssl_trust_store setting. SERVER-2944

Resolved issues

RPM should create puppet user with UID/GID 52. When the puppet user and group are created on rpm-based systems, they are now assigned a static UID/GID of 52. SERVER-1381

Puppet Server 7.7.0

Released April 2022 and shipped with Puppet 7.16.0.

Enhancements

Change Dropsonde telemetry to Opt-out. Metrics will now be collected with Dropsonde by default. To opt out of metrics collection, configure dropsonde: { enabled: false } in puppetserver.conf. By default, Dropsonde collects metrics when the service is started, and once a week thereafter. SERVER-3170

Enable sles-15-x86_64 builds and testing for puppetserver. We now support puppetserver on sles-15-x86_64. SERVER-3156

Puppet Server 7.6.1

Released March 2022 and shipped with Puppet 7.15.0.

Enhancements

Bump BouncyCastle to 1.70. Puppet Server now ships with Bouncy Castle 1.70, which has improved TLS 1.3 support. SERVER-3135

Rocky and Alma support. Puppet Server is now being tested on Rocky and Alma Linux. Use the EL8 packages on these operating systems. SERVER-3099

JRuby pool lock lifecycle logging. The JRuby lock lifecycle of request, acquire, and release is now logged at the INFO level, rather than DEBUG. SERVER-3098

Resolved issues

Bad exit code for errors in puppetserver ca list. The puppetserver ca list command will now exit 1 when run on a non-CA server. SERVER-2797

Puppet Server CA always creates type 1 authority key identifiers. Previously, Puppet Server would always compute a type 1 key identifier based on the public key of the certificate authority. This is incompatible in situations where Puppet Server imports pre-made certificates that use a type 2 key identifier.

Now, Puppet Server will copy the subject key identifier from the ca certificate instead of computing a type 1 key identifier. This will allow for type 2 identifiers and future key types on the CA. With this change, Puppet Server can now use an intermediate certificate authority signed by HashiCorp’s Vault or AWS ACM. SERVER-2662

Puppet Server 7.6.0

Released January 2022 and shipped with Puppet 7.14.0.

Enhancements

Debian support. Puppet Server is now packaged for Debian 11. It requires Java 11 to be installed. SERVER-3137

Resolved issues

CA Authority Key Identifier incorrectly filled with issuer instead of keyid. The self-signed CA signing cert generated by starting puppetserver will now use a keyid for its authority key identifier to match the CA chain generated by puppetserver ca setup. SERVER-3114

CA added a Subject Alternative Name extension to CA certs The CA signing cert no longer has subject alternative names added to it, since they are not meaningful. SERVER-3114

Puppet Server 7.5.0

Released December 2021 and shipped with Puppet 7.13.1.

Enhancements

Metrics collection with Dropsonde. Users can now enable module metrics collection via Dropsonde. To turn this on, configure dropsonde: { enabled: true } in puppetserver.conf. By default when enabled, Dropsonde collects metrics when the service is started and once a week thereafter. SERVER-3079

Resolved issues

CRL uploading. The CRL update endpoint will now issue a meaningful error message when a CRL without an authority key identifier is sent in the request body. SERVER-3080

Deprecations

el6 support. Removed support for el6 as a server platform.

Puppet Server 7.4.2

Released November 2021 and shipped with Puppet 7.12.1.

This release includes security fixes. For the latest features, see the release notes for Server 7.4.1

Puppet Server 7.4.1

Released October 2021 and shipped with Puppet 7.12.0.

Enhancements

Retrieve facts from any terminus. The v4 catalog endpoint (used by Impact Analysis) now supports retrieving facts from any facts terminus, if none are provided with the request. SERVER-3050

Puppet Server 7.4.0

Released September 2021 and shipped with Puppet 7.11.0.

Enhancements

TLS 1.3 support. Puppet Server now supports TLS 1.3 and associated cipher suites by default. SERVER-3076

Improved performance in list command. Puppetserver CA CLI command list utilizes the updated certificate_status endpoint for a faster performance when listing certificate requests. SERVER-3060

--force flag in certificate generation. The puppetserver ca generate --ca-client command can now take a --force flag, which forces the tool to generate the certificate even if it cannot determine whether Puppet Server is offline. To avoid CA corruption, ensure your server is offline before you use this flag. SERVER-2842

Puppet Server 7.3.0

Released August 2021 and shipped with Puppet 7.10.0.

Enhancements

Prune duplicate entries from CRL. In this release, the puppetserver ca subcommand now accepts the prune actions. These actions allow you to prune any duplicate certificates from Puppet’s CRL. SERVER-2740

CRL query speed. Querying CRLs from puppetserver is now faster, resulting in fewer timeouts. SERVER-3020

Scripts as a default mount. Puppet Server has a new default mount named scripts. You can use the new default mount with API endpoints such as file_content, file_metadata, and static_file_content to load scripts from the scripts/ directory of a module. SERVER-3058

Resolved issues

Duplicate entries in CRL. Puppet CA no longer allows adding duplicate certificates to the CRL. SERVER-2509

Puppet Server 7.2.1

Released July 2021 and shipped with Puppet 7.9.0.

Enhancements

  • Add new flag. In this release, the puppetserver ca subcommand now accepts the --verbose flag. If the --verbose flag is passed, it displays additional low-level details about the invoked action (such as details about HTTP requests created by the tool). SERVER-2251

  • Specify certificate output in JSON. In this release, the puppetserver ca list action now accepts a --format flag that can be used to display certificates in JSON format. The output format is text by default. SERVER-3006

  • Jetty 9.4.42. This release includes a Jetty update to 9.4.42. SERVER-3035

Resolved issues

  • CRL update endpoint is not enabled by default. The PUT /puppet-ca/v1/certificate_revocation_list endpoint is now enabled by default for clients that have a special cert extension. Previously, you had to manually update the auth.conf file to access this endpoint. SERVER-3033

  • Puppet Server cannot use OpenSSL EC files in OpenSSL format. Previously, Puppet Server failed to load private key PEM files that include separate blocks for EC parameters (such as files output by OpenSSL’s EC key gen commands). This issue is now fixed. SERVER-3016

  • A command errors because of the subject alternative name. The puppetserver ca generate command no longer errors when allow-subject-alt-names is set to false. SERVER-3032

Puppet Server 7.2.0

Released May 2021 and shipped with Puppet 7.7.0 and Puppet 7.8.0.

New Features

  • The CA API accepts CRL updates. You can now update your CRLs using the new API endpoint: PUT /puppet-ca/v1/certificate_revocation_list. This new endpoint accepts a list of CRL PEMs as a body, inserting updated copies of the applicable CRLs into the trust chain. The CA updates the matching CRLs saved on disk if the submitted ones have a higher CRL number than their counterparts. You can use this endpoint if your CRLs require frequent updates. Do not use the endpoint to update the CRL associated with the Puppet CA signing certificate (only earlier ones in the certificate chain). SERVER-2550

Enhancements

  • JRuby 9.2.17.0. In this release, the JRuby version is updated to 9.2.17.0. SERVER-3007

Resolved issues

  • New apache HTTP client broke URL normalization. A security update to the apache HTTP client introduced an unrelated change to URL normalization. This change affected any use of Puppet’s HTTP client within Puppet Server. In this release, the double slash in a URL path is no longer silently ignored by the HTTP client in Puppet Server. Instead, Puppet Server views it as a different URL and returns a 404. Going forward, remove leading double slashes from URLs. SERVER-3014

  • Environment endpoint failed to cache data if given valid etag. Previously, if you used the environment and transport info endpoints, then you might have seen the cache bypassed—despite receiving a 304 Not Modified response. To work around this issue, users must submit a request to the environment_classes endpoint without the etag. This request triggers the correct caching behavior. Note that the console (the consumer of the environment_classes endpoint in PE) must always submit an etag for an environment if it has one. SERVER-3015

Puppet Server 7.1.2

Released April 2021 and shipped with Puppet 7.6.1.

This release includes minor dependency updates, including an update to Jetty 9.4.40 to resolve security issues.

Puppet Server 7.1.0

Released March 2021 and shipped with Puppet 7.5.0.

Enhancements

  • Puppet Server adds SAN when signing CSR. Puppet Server now adds an extension for subject-alternative-name (SAN) when it signs incoming certificate signing requests (CSR). The SAN extension contains the common name (CN) as a dns-name on the certificate. If the CSR comes with its own SAN extension, Puppet Server signs it and ensures the SAN extension includes the CSR’s CN. SERVER-2338

Resolved issues

  • Attempts to start a compile master failed with a CRL error. The Jetty webserver now uses the local copy of the CRL from Puppet's SSL directory instead of the CA's copy. This fix makes it easier to set up compilers, which always have a disabled CA service and no CRL at the CA path. SERVER-2558

Deprecations

  • Puppet Server's updated configuration values. The master-conf-dir, master-code-dir, master-var-dir, master-log-dir, and master-run-dir configuration settings have been deprecated in favor of server-conf-dir, server-code-dir, server-var-dir, server-log-dir, and server-run-dir respectively. The configuration files — which use the new settings — are shipped with the 7.1.0 puppetserver package. Note that the old settings are still honored for backwards compatibility, but we recommend you upgrade to the new settings. SERVER-2867

Puppet Server 7.0.3

Released February 2021 and shipped with Puppet 7.4.0.

This release updates dependencies to include security fixes.

Puppet Server 7.0.2

Released January 2021 and shipped with Puppet 7.3.0.

Resolved issues

  • Puppet Server failed to issue a warning for the applicable behavior. The warning issued when the CA directory is inside the SSL directory now only prints server logs at startup and when using the puppetserver ca CLI, instead of any time a Puppet command is used. (SERVER-2934)

Puppet Server 7.0.1

Released December 2020 and shipped with Puppet 7.1.0.

Enhancements

  • JRuby 9.2.14.0. The JRuby version has been bumped from 9.2.13.0 to 9.2.14.0. (SERVER-2925)

  • Symlink from the previous cadir has the same permissions as the current cadir. When creating the symlink between the new and legacy cadirs the symlink will now be properly owned by the puppet user. (SERVER-2917)

Resolved issues

  • CA command line tool failed to honor a section in Puppet's configuration file. The CA command line tool now correctly honors the server sections in the puppet.conf.

Puppet Server 7.0.0

Released November 2020 and shipped with Puppet 7.0.0.

Puppet Server 7.0 is a major release. It breaks compatibility with agents prior to 4.0 and the legacy Puppet auth.conf, moves the default location for the cadir, and changes defaults for fact caching and cipher suites. See below for more details. Caution is advised when upgrading.

New features

  • The default value for the cadir setting is now located at /etc/puppetlabs/puppetserver/ca. Previously, the default location was inside Puppet's own ssldir at /etc/puppetlabs/puppet/ssl/ca. This change makes it safer to delete Puppet'sssldir without accidentally deleting your CA certificates.

  • The puppetserver CA CLI now provides a migrate command to move the CA directory from the Puppet confdir to the puppetserver confdir. It leaves behind a symlink on the old CA location, pointing to the new location at /etc/puppetlabs/puppetserver/ca. The symlink provides backwards compatibility for tools still expecting the cadir to exist in the old location. In a future release, the cadir setting will be removed entirely. (SERVER-2896)

  • The default value for the facts cache is now JSON instead of YAML. You can re-enable the old YAML terminus in routes.yaml. (PUP-10656)

  • Support for legacy Puppet auth.conf has been removed and the jruby-puppet.use-legacy-auth-conf setting no longer works. Use Puppet Server's auth.conf file instead. (SERVER-2778)

  • Puppet Server no longer services requests for legacy (3.x) Puppet endpoints. Puppet Agents before 4.0 are no longer be able to check in. (SERVER-2791)

  • This release removes default support for many cipher suites when contacting Puppet Server. The new default supported cipher suites are: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, and TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384. This change aligns open source Puppet with Puppet Enterprise. Note that this change may break on old platforms. To re-enable older cipher suites you may edit the webserver.conf. Valid cipher suite names are listed in the JDK Documentation. (SERVER-2913)

  • Puppet Server now provides an HTTP client whose API conforms to the HTTP client provided by Puppet. This new client is stored in the Puppet runtime as Puppet.runtime[:http]. (SERVER-2780)

Puppet Server known issues

For information about currently known issues, see the following list.

Access CA endpoint to update CRLs

Puppet Server 7.2.0 and 6.16.0 include the following new API endpoint: PUT /puppet-ca/v1/certificate_revocation_list. To update this endpoint, you must update the endpoint's rule to be type regex instead of path in the configuration file at /etc/puppetlabs/puppetserver/conf.d/auth.conf.

Cipher updates in Puppet Server 6.5

Puppet Server 6.5 includes an upgrade to the latest release of Jetty's 9.4 series. With this update, you may see "weak cipher" warnings about ciphers that were previously enabled by default. Puppet Server now defaults to stronger FIPS-compliant ciphers, but you must first remove the weak ciphers.

The ciphers previously enabled by default have not been changed, but are considered weak by the updated standards. Remove the weak ciphers by removing the cipher-suite configuration section from the webserver.conf. After you remove the cipher-suite, Puppet Server uses the FIPS-compliant ciphers instead. This release includes the weak ciphers for backward compatibility only.

The FIPS-compliant cipher suites, which are not considered weak, will be the default in a future version of Puppet. To maintain backwards compatibility, Puppet Server explicitly enables all cipher suites that were available as of Puppet Server 6.0. When you upgrade to Puppet Server 6.5.0, this affects you in in two ways:

  1. The 6.5 package updates the webserver.conf file in Puppet Server's conf.d directory.

  2. When Puppet Server starts or reloads, Jetty warns about weak cipher suites being enabled.

This update also removes the so-linger-seconds configuration setting. This setting is now ignored and a warning is issued if it is set. See Jetty's so-linger-seconds for removal details.

Note: On some older operating systems, you might see additional warnings that newer cipher suites are unavailable. In this case, manage the contents of the webserver.cipher-suites configuration value to be those strong suites that available to you.

Potential JAVA ARGS settings

If you're working outside of lab environment, increase ReservedCodeCache to 512m under normal load. If you're working with 6-12 JRuby instances (or a max-requests-per-instance value significantly less than 100k), run with a ReservedCodeCache of 1G. Twelve or more JRuby instances in a single server might require 2G or more.

Similar caveats regarding scaling ReservedCodeCache might apply if users are managing MaxMetaspace.

tmp directory mounted noexec

In some cases (especially for RHEL 7 installations) if the /tmp directory is mounted as noexec, Puppet Server may fail to run correctly, and you may see an error in the Puppet Server logs similar to the following:

Nov 12 17:46:12 fqdn.com java[56495]: Failed to load feature test for posix: can't find user for 0
Nov 12 17:46:12 fqdn.com java[56495]: Cannot run on Microsoft Windows without the win32-process, win32-dir and win32-service gems: Win32API only supported on win32
Nov 12 17:46:12 fqdn.com java[56495]: Puppet::Error: Cannot determine basic system flavour

This is caused by the fact that JRuby contains some embedded files which need to be copied somewhere on the filesystem before they can be executed (see this JRuby issue). To work around this issue, you can either mount the /tmp directory without noexec, or you can choose a different directory to use as the temporary directory for the Puppet Server process.

Either way, you'll need to set the permissions of the directory to 1777. This allows the Puppet Server JRuby process to write a file to /tmp and then execute it. If permissions are set incorrectly, you'll get a massive stack trace without much useful information in it.

To use a different temporary directory, you can set the following JVM property:

-Djava.io.tmpdir=/some/other/temporary/directory

When Puppet Server is installed from packages, add this property to the JAVA_ARGS and JAVA_ARGS_CLI variables defined in either /etc/sysconfig/puppetserver or /etc/default/puppetserver, depending on your distribution. Invocations of the gem, ruby, and irb subcommands use the updated JAVA_ARGS_CLI on their next invocation. The service will need to be restarted in order to re-read the JAVA_ARGS variable.

Puppet Server Fails to Connect to Load-Balanced Servers with Different SSL Certificates

SERVER-207: Intermittent SSL connection failures have been seen when Puppet Server tries to make SSL requests to servers via the same virtual ip address. This has been seen when the servers present different certificates during the SSL handshake.

Facter 4 known issues

These are the known issues in this version of Facter.

Facter 4.7.1 cannot collect Google Cloud metadata

Because of a regression, Facter 4.7.1 cannot collect or read Google Cloud metadata. A fix has been identified and is scheduled for inclusion in the next Puppet releases. #2731

The implementation of the dot notation is not compatible with the Puppet ecosystem

The implementation of the dot notation feature is not compatible with other parts of the Puppet ecosystem, and does not give the fact the same name as Facter 3. For example, the supported puppetlabs-lvm module creates facts for each volume group in the form of lvm_vg_<name>_pvs. If the volume group name contains a dot, Facter converts the fact from a legacy fact to a structured fact. To access the fact using Puppet's dotted notation, you would need to change your Puppet manifests, Hiera lookups, and Puppet Enterprise (PE) classification rules, causing breaking changes. As a result, Facter 4.1 reverts back to the way Facter 3 handled facts with dotted names.

If you want to re-enable the Facter 4 behaviour — that converts a dotted fact to a structured fact — add the following setting to your manifest:
global : {
    force-dot-resolution : true
}

FACT-3004

Incorrect OS description output on Debian 9

Running the facter command in Facter 4 returns incorrect output for the os.distro.description fact on Debian 9. This facts work correctly in Facter 3 and appears differently when running the puppet facts diff command. FACT-2985

Incorrect output of the processors.speed fact on Linux

This is issue affects non-virtualized systems — with processors that support variable frequency. FACT-2980

Upgrading from open source Puppet to Puppet Core

To help ensure a smooth transition from open source Puppet to Puppet Core, upgrade from open source Puppet 7.34.0 to Puppet Core 7.35.0. These two product versions are nearly identical, so an upgrade is possible without significant post-upgrade adjustments. However, if you select a different upgrade path, or you customized your Puppet Core infrastructure, you might have to introduce additional adjustments.

Tip: When you purchase Puppet Core, you are entitled to contact the Professional Services team, which can assist you with the upgrade process.

Upgrade prerequisites

  • To obtain access to the installation packages, follow the instructions in Purchasing Puppet Core.
  • Because Puppet Core packages are in a protected repository, which requires authentication, disable the access that you previously established to the public open source repository. This action is necessary to access Puppet Core packages.
  • Back up your installation.
You do not have to uninstall previously installed packages.

Upgrade procedure

For instructions, see Upgrading.

Upgrading from Puppet 6 to Puppet 7.34.0 or earlier

Before upgrading to open source Puppet 7.34.0 or earlier, review the following recommendations and changes so that you can plan your upgrade accordingly.

Note that this list is not intended to be exhaustive. It highlights changes that might require action after you upgrade. For a full list of changes, including all deprecations and removals, see the Puppet 7 release notes.

Important: Starting with V7.35.0, open source Puppet is renamed to Puppet Core, and installation packages are in a protected repository. For instructions about upgrading to Puppet Core, see Upgrading from open source Puppet to Puppet Core.
Important: Always back up your installation before performing any upgrade.

Upgrade to Puppet 6.22.0 and run the puppet facts diff command

Note: This is the only action we recommend before you upgrade. If you do not need to see the differences between the Facter 3 and Facter 4 output, you can upgrade to Puppet 7 from any version of Puppet 6.

If you are currently using Puppet 6.21.0 or below, upgrade to Puppet 6.22.0 before you upgrade to Puppet 7, and run the puppet facts diff command to see if there are any output differences between Facter 3 and Facter 4. Puppet 6.22.0 filters out the core volatile facts and provides an --exclude flag that allows to exclude specific facts.

When you run the puppet facts diff command, the output looks something like:
> puppet facts diff
{
  "fact_with_different_values": {
    "new_value": "facter4",
    "old_value": "facter3"
  },
  "fact_not_existing_in_facter3": {
    "new_value": "facter4",
    "old_value": null
  },
  "fact_not_existing_in_facter4": {
    "new_value": null,
    "old_value": "facter3"
  }
}


new_value  - the value in Facter 4
old_value  - the value in Facter 3

Some of the differences you might see include:

  • A volatile fact that comes from a module, for example the puppet_agent_pid fact from the puppet_agent module.

  • Facts that return an Array as a value. For example the mountpoints fact has an options field. The puppet facts diff command reports these differences because the value Array can be in a different order. For example:
    # facter 3 output
    > facter mountpoints./.options
    [ "local", "noatime", "nobrowse", "journaled"]
    
    # facter 4 output
    > facter mountpoints./.options
    [ "local", "nobrowse", "journaled", "noatime"]
    
          ❯ puppet facts diff
                   "mountpoints./.options.2": {
              "new_value": "nobrowse",
              "old_value": "noatime"
            },
            "mountpoints./.options.3": {
              "new_value": "journaled",
              "old_value": "nobrowse"
            },
            "mountpoints./.options.4": {
              "new_value": "noatime",
              "old_value": "journaled"
            }
  • New facts. For example, Facter 4 added cores and threads information to the processors fact. These return the following diff output:
    {
      "processors.cores": {
        "new_value": 2,
        "old_value": null
      },
      "processors.threads": {
        "new_value": 1,
        "old_value": null
      }
    }
If you see differences caused by a Facter 3 known issue, you can use the --exclude flag to remove them from your output, so that you only see the differences relevant to you. For example:
# using --exclude flag to filter out multiple facts
> puppet facts diff --exclude "^fact1$|^fact2$"
{
  "fact3": {
    "new_value": null,
    "old_value": "facter3"
  }
}
The puppet facts diff command is also available as a task in the puppetlabs-puppet_agent module version 4.5.0 or above. Starting with version 4.5.1, the exclude parameter is available. For example:
> bolt task show puppet_agent::facts_diff
puppet_agent::facts_diff
  Run the Puppet agent facts diff action

Usage
  bolt task run puppet_agent::facts_diff --targets <targets> [exclude=<value>]

Parameters
  exclude  Optional[String]
    Regex used to exclude specific facts from diff.
Note: For information on a specific fact, see the known issues and release notes for both Facter 3 and Facter 4.

Update the acl and reboot modules

If you want to use the acl and reboot modules with Puppet 7, you need to update them to the following versions:

New CA directory location

The default location of the CA directory in Puppet 7 is etc/puppetlabs/puppetserver/ca. The new location makes it harder to accidentally delete your CA. When you upgrade to Puppet 7, we do not move the CA directory for you. The puppetserver CA CLI provides a migrate command for you to move your CA directory to the new location — puppetserver ca migrate. This creates a symlink from the old CA location to the new location. The symlink provides backwards compatibility for tools still expecting the cadir to exist in the old location. In a future release, the cadir setting will be removed entirely.

The local filebucket is disabled by default

The Puppet 7 local filebucket is disabled by default as the local cache has no limit and is not automatically cleaned. To clean the local cache, run the puppet_agent::delete_local_filebucket task from the puppetlabs-puppet_agent module version 4.5.1 or above. For example:
> bolt task show puppet_agent::delete_local_filebucket
puppet_agent::delete_local_filebucket
  Removes the local filebucket

Usage
  bolt task run puppet_agent::delete_local_filebucket --targets <targets>
  [force=<value>]

Parameters
  force  Optional[Boolean]
    ignore nonexistent files and errors

Windows win32 gems removed

Custom facts, external facts, and modules that explicitly require (or rely on Puppet to provide) win32 gems do not work in Puppet 7. These include:
  • win32-process
  • win32-service
  • win32-dir
  • win32-security
CAUTION: We are not validating the win32 gems with Ruby 2.7. If you choose to install them, expect deprecation warnings.

The win32-service gem

The win32-service gem allows you to control or create MS Windows services. The functionality that the win32-service gem provided is available in Puppet 7 with the Puppet::Util::Windows::Service class, and provides the following methods: [:send_service_control_signal, :resume, :start, :service_start_type, :service_state, :stop, :logon_account, :set_startup_configuration, :services, :exists?].

To use the Puppet::Util::Windows::Service class instead of the Win32::Service gem, make the following changes to your configuration:

  • Remove require win32/service.

  • Replace Win32::Service with Puppet::Util::Windows::Service.

If you need any other win32-service functionality — that is not provided by Puppet::Util::Windows::Service — add the following code to your manifest:
package { 'win32-service':
  ensure   => ['0.8.8'],
  provider => 'puppet_gem',
}

This keeps the win32-service gem locked on version 0.8.8.

The win32-process gem

The win32-process gem provided Ruby’s monkey-patching Process class. Puppet 7 implements part of this functionality and exposes the following methods: [:create, :setpriority].

To use the Puppet 7 functionality instead of the win32-process gem, make the following changes to your configuration:

  • Remove require win32-process.
  • Add require 'puppet' (Windows users only).
If you need any additional win32-process functionality — that is not provided by Puppet 7 — add the following code to your manifest:
package { 'win32-process':
 ensure => ['0.7.5'],
 provider => 'puppet_gem',
}

The win32-security gem

There is no replacement provided by Puppet for the win32-security gem. Remove require 'win32-security' from your code.

If a particular module requires this gem, you can install it by adding the following code to your manifest:
package { 'win32-security':
 ensure => ['0.4.9'],
 provider => 'puppet_gem',
}

The win32-dir gem

There is no replacement for the win32-dir gem. Puppet now relies on environment variables for this functionality. Remove any require 'win32-dir' from your code and replace the Dir calls with the corresponding environment variables, if possible. For example, if you have a custom fact that references Dir::COMMON_APPDATA, replace it with the corresponding environment variable ENV['ALLUSERSPROFILE'].

If a particular module requires this gem, you can install it by adding the following code to your manifest:
package { 'win32-dir':
 ensure => ['0.4.9'],
 provider => 'puppet_gem',
}
Note: Puppet 7 has also removed the http-client and pathspec gems for all operating systems. For a full list of removed gems, see deprecations and removals.

Facter 4 dotted facts

Facter 4, which ships with Puppet 7, introduced a new way to write aggregate custom facts by using a dot notation in a fact name. Facter automatically combines the two facts and creates a structured fact. However, in Facter 4.0.52 and below, the implementation of feature is not compatible with other parts of the Puppet ecosystem, and does not give the fact the same name as Facter 3. As a result, Facter 4.1 reverted back to the way Facter 3 handled facts with dotted names. If you want to re-enable the Facter 4 behaviour — that converts a dotted fact to a structured fact — add the following setting to your manifest:
global : {
    force-dot-resolution : true
}

What's new since Puppet 6?

These are the major new features, enhancements, deprecations, and removals since the Puppet 6 release.

Note that this list is not intended to be exhaustive.

Get familiar with the latest hardware requirements, supported operating systems and browsers, and network configuration details in System requirements.

Facter 4

Facter 4 introduces new features, including granular blocking and caching of all types of facts, user defined fact groups, fact hierarchies using the dot notation and profiling using the --timing option. Facter 4 is written in Ruby, instead of C++. It is API compatible with Facter 3, but there may be some inconsistencies. Puppet 7 drops support for Facter 3.

Ruby 2.7

Puppet 7 agents have upgraded to Ruby 2.7 and dropped support for Ruby 2.3 and 2.4. After upgrading to Puppet 7, use the puppet_gem provider to ensure all your gems are installed.

Postgres 11+

PuppetDB now requires Postgres 11+, which allows us to write faster migrations and take advantage of newer features like logical partitioning.

Environment caching

The Puppet 7 environment_timeout behaves differently for values that are not 0 or unlimited. Puppet Server keeps your most actively used environments cached, but allows testing environments to fall out of the cache and reduce memory usage

SHA256

Puppet 7 defaults to using SHA256 for all digest operations. MD5 is still be available for non-FIPS platforms, but you must opt into it using the checksum parameter for a file resource.

CAUTION: To avoid breaking changes when upgrading, either disable remote filebuckets or make sure the agent has the same digest algorithm as server by changing the digest_algorithm setting on the agent to sha256.

CA directory

We have made changes to prevent you from accidentally deleting your CA directory. This change is backwards compatible.

Puppet language enhancements

The Puppet 7 compiler raises syntax errors if it encounters application orchestration language keywords. These keywords remain reserved for future use.

Platform end-of-life

We have dropped agent support for the following platforms: EL5, Debian 8, SLES 11, Ubuntu 14.04, and Windows 2008/2008R2. Puppet Server and PuppetDB platforms have not changed.

Removals

We've removed the following deprecated functionality:

  • Legacy authorization — replaced by Puppet Server's auth.conf in Puppet 5.
  • Legacy routes — Puppet 3 agents are no longer be able to communicate with these.
  • Puppet key, cert and status commands.

Documentation terminology changes

Documentation for this release replaces the term master with primary server. This change is part of a company-wide effort to remove harmful terminology from our products. For the immediate future, you’ll continue to encounter master within the product, for example in parameters, commands, and preconfigured node groups. Where documentation references these codified product elements, we’ve left the term as-is. As a result of this update, if you’ve bookmarked or linked to specific sections of a docs page that include master in the URL, you’ll need to update your link.

Experimental features

Released versions of Puppet can include experimental features to be considered for adoption but that are not yet ready for production. These features need to be tested in the field before they can be considered safe, and therefore are turned off by default.

Experimental features can have a solid design but with an unknown performance and resource usage. Sometimes even the design is tentative, and because of this, we need feedback from users. By shipping these features early in disabled form, we want it to be easier for testing and giving feedback.

Risks and support

CAUTION: Experimental features are not officially supported by Puppet, and we do not recommend that you turn them on in a production environment. They are available for testing in relatively safe scratch environments, and are used at your own risk.

Puppet employees and community members do their best to help you in Puppet Community Slack channels and in Puppet mailing lists, but we make no promises about experimental functionality.

Enabling experimental features might degrade the performance of your Puppet infrastructure, interfere with the normal operation of your managed nodes, introduce unexpected security risks, or have other undesired effects.

If Puppet Support is assisting you with a problem, we might ask you to disable any experimental features.

Changes to experimental features

Experimental features are exempt from semantic versioning, which means that they can change at any time, and are not limited to major or minor release boundaries.

These changes might include adding or removing functionality, changing the names of settings and other affordances, and more.

Documentation of experimental features

The Puppet documentation contains pages for any currently available experimental features. These pages are focused on enabling a feature and running through the interesting parts of its functionality; they might lag slightly behind the feature as implemented.

When a feature has experienced major changes across minor versions, we note the differences at the top of that feature page.

Each feature page attempts to give some context about the status of that feature and its prospects for official release.

Giving feedback on experimental features

To help us keep improving Puppet, tell us more about your experience. Let us know what works, and what doesn't. The Puppet Community supports many communication options, including Slack channels and mailing lists. For more information, see Welcome to the Puppet Community.

Archived documentation

Open source Puppet documentation for recent end-of-life (EOL) product versions is archived. You can access archived-in-place documentation by using the original URLs, or from the links here.

For the latest official open source Puppet documentation for V7, see Open source Puppet 7.34.0.

Open source Puppet documentation for EOL versions earlier than those listed here is archived in our open source Puppet docs archive.