Puppet Enterprise 2019.8.10 is now available!

1 view
Skip to first unread message

Puppet Product Updates

unread,
Feb 15, 2022, 7:09:47 PM2/15/22
to

The latest patch release for the current Long Term Support (LTS) version of Puppet Enterprise, 2019.8.10, is now available!

 

This is a backward-compatible release that contains enhancements and bug fixes, including:

 

Enhancements: 

  • Bypass node verification failure when primary server certificates are damaged. You can use --force to bypass node verification failure and force certificate regeneration when your primary server certificates are damaged.

  • Simplified login error message. The Puppet Enterprise (PE) console login error message instructs the user to contact an administrator rather than consult the console-services log.

  • Improved disk usage when syncing certificate authority data. Disk usage is better when syncing certificate authority data between the primary and replica.

  • Agent support for:

    • Microsoft Windows Server 2022 x86_64

    • Red Hat Enterprise Linux 9 x86_64

  • Patch management:

    • Amazon Linux 2

 

Deprecations and removals: 

Support for these platforms is deprecated in this release:  

  • Primary server: 

    • CentOS 8

  • Agent:

    • CentOS 8

 

Resolved in this release:

 

  • Expired GPG key caused install failures. The GPG key bundled with PE versions prior to 2019.8.4 expired on 17 August 2021, which could cause a failure when PE packages are being added to the system. Customers upgrading to a newer version are no longer affected.

  • Packages were not marked as automatically installed by APT if you set security_only to true. When running the pe_patch::patch_server task with the security_only parameter set to true, packages were not marked as being automatically installed by APT. This caused problems if you rely on this marking for APT autoremove to remove old packages. The patch_server task now marks packages as automatically installed, regardless of the security_only parameter.

  • r10k can recover from typos in the config or Puppetfile. r10k now updates its cache repos when the remote URL changes. This allows r10k to recover from typos in the config or Puppetfile.

  • Couldn't complete restoration if the r10k_remote parameter wasn't set. The r10k_remote parameter wasn't set when restoring a backup with scope set to certs, code, or puppetdb. This prevented you from finishing restoration because the commands necessary to finish restoring your primary server did not print.

  • The fail_plan function didn't show custom error information. The fail_plan function ignored the kind and details parameters, which are used to specify custom, machine-parseable information about an error.

  • Scheduled jobs failed on FIPS installs. Scheduled jobs, including tasks and plans, couldn't run or be listed on FIPS installs of PE and resulted in the error javax.crypto.BadPaddingException.

 

Check out the release notes: https://puppet.com/docs/pe/2019.8/release_notes_pe_index.html

 

Important note: If you are using Continuous Delivery for PE, upgrade to CD4PE 4.8.2 prior to upgrading to Puppet Enterprise 2019.8.10. We resolved a PuppetDB issue causing the generation of new fact charts on the Nodes page to fail.

 

Download PE 2019.8.10 here: https://puppet.com/misc/pe-files/previous-releases/2019.8.10

 

As a current Puppet Enterprise user, you can update to this new version as part of your annual subscription. When updating, you must update infrastructure components first and then update agents. For detailed instructions, see the documentation.


Reply all
Reply to author
Forward
0 new messages