We are planning for Ubuntu 20.04 PE primary server support on our next Puppet Enterprise release planned for May.
Cheers! Alex Rodriguez Technical Program Manager, R&D On Thursday, February 17, 2022 at 7:38:43 PM UTC-8 [email protected] wrote: > Thanks for the new platform support. > > Any idea on when we'll see Ubuntu 20.04 as a supported platform for the > main PE server? > > On Tuesday, February 15, 2022 at 6:58:50 PM UTC-5 Puppet Product Updates > wrote: > >> The latest release for the Puppet Enterprise release track, PE 2021.5, is >> now available! >> >> >> >> Enhancements in this release include: >> >> >> - >> >> 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. >> - >> >> Improved disk usage when syncing certificate authority data. Disk >> usage is better when syncing certificate authority data between the >> primary >> and replica. >> - >> >> Primary server support for: >> - >> >> Amazon Linux 2 >> - >> >> Agent support for: >> - >> >> Microsoft Windows Server 2022 x86_64 >> - >> >> Red Hat Enterprise Linux 9 x86_64 >> - >> >> Patch management: >> - >> >> Amazon Linux 2 >> >> >> >> Resolved in this release: >> >> - >> >> 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. >> - >> >> Schedule task button sometimes failed to redirect. When scheduling a >> task to run at some later time or interval, under some circumstances, >> clicking Schedule task did not redirect you to the Scheduled tasks page. >> - >> >> 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/2021.5/release_notes_pe_index.html >> >> >> >> Important note: If you are using Continuous Delivery for PE, upgrade to >> CD4PE 4.8.2 or a newer version prior to upgrading to Puppet Enterprise >> 2021.5. We resolved a PuppetDB issue causing the generation of new fact >> charts on the Nodes page to fail. >> >> >> >> *Download PE 2021.5 here*: >> https://puppet.com/try-puppet/puppet-enterprise/download/ >> >> >> 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 >> <https://puppet.com/docs/pe/2021.5/upgrading_pe.html>. >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/970d092e-270e-4858-83c1-7d24fb9bed8en%40googlegroups.com.
