Puppet Platform 7.3.0 is now available
Puppet Product Updates
The next release in the Puppet 7 series, Puppet 7.3.0, is now available!
The release contains bug fixes and minor improvements, including:
PUP-10725 -The serverport setting as alias for masterport
PUP-10795 - Multiple logdest locations in puppet.conf accepted
PUP-9176 - 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-10850 - New --no-legacy option to disable legacy facts on the puppet facts application
PUP-10845 - Eliminate Ruby 2.7.x warnings when running puppet apply with node statements
PUP-10840 - Remove Pathname#cleanpath Ruby 1.9 workaround
PUP-10851 - 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-10819 - Allow calling deferred 3.x functions, like sprintf during a Puppet agent run
PUP-10818 - 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-10847 - ‘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-10842 - Issue with Puppet creating production folder when multiple environment paths are set
Previously, the production environment folder was automatically created at every Puppet run, 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.
FACT-2919 - Aggregate facts are broken.
Previously, Facter broke when trying to add a debug message for the location where aggregate facts are resolved from. This only happened with aggregate facts that returned an array or hash without having an aggregate block call.
FACT-2882 - Facter 4.0.x does not return the domain correctly when set in the registry.
Previously, Facter did not retrieve the domain correctly on Linux and resulted in faulty FQDN facts. Facter also failed to retrieve domain facts when Windows did not expose the host's primary DNS suffix. This is now fixed.FACT-2911 - Legacy group blocks ‘processors’ core fact. Blocking legacy facts no longer blocks ‘processors’ core fact.
FACT-2909 - Added Facter Hocon output format.
FACT-2903 - Legacy blockdevice vendor and size facts not resolving. This release fixes blockdevice_*_size facts not resolving on AIX, and blockdevice_*_vendor facts not resolving on Linux and Solaris.
FACT-2902 - Facter detects os family without checking or translating the information.
Previously, Facter detected the os family by reading /etc/os-release without checking or translating the information. This is now fixed and Facter translates the ID_LIKE field from /etc/os-release to Facter known families.
The warning issued when the CA dir is inside the SSL dir 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)