Installing and upgrading
- KB#0102 Expired GPG Key causes node installation to fail in Puppet Enterprise 2016.2 and earlier
- KB#0401 Confirming that your PE installation is ready for an upgrade
- KB#0362 Use a task to stay up to date with Puppet Enterprise z releases for PE 2017.3 and later
- KB#0345 Upgrade Puppet Enterprise with high availability enabled and no agent downtime
- KB#0344 Installing the Windows agent with PowerShell fails with the error "Could not create SSL/TLS secure channel" in Puppet Enterprise 2018.1.x to 2019.0.3
- KB#0329 After installing or upgrading to PE 2019.0.2 with Continuous Delivery for PE impact analysis enabled, pe-puppetserver fails to start
- KB#0321 Prevent the puppetlabs-puppet_agent module from overwriting puppet.conf settings during Windows agent upgrades in Puppet Enterprise
- KB#0304 "fast_gettext" error in Puppet Enterprise when upgrading from Puppet agent 5.3.3 (PE 2017.3.2) and earlier to 5.3.4 (PE 2017.3.4) and later
- KB#0293 Completely remove the previous version of the Puppet Plug-in for VMware vRealize Automation plug-in when installing the latest plug-in
- KB#0234 Puppet Plug-in v3.0 and 3.1 for vRealize Automation: adding a Puppet master fails in Puppet Enterprise 2016.4.x to 2018.1.x
- KB#0103 Check your preconfigured node groups when installing or upgrading Puppet Enterprise 2017.2.x, 2017.1.x, or 2016.x
- KB#0104 Installing or upgrading fails while searching for "/opt/puppet/share/locale/config.yaml" in Puppet Enterprise 2017.1.x or 2017.2.1
- KB#0105 Upgrading to Puppet Enterprise 2016.4.x from PE 2015.3 and earlier fails with a "java.lang.AssertionError: Assert failed: the secret key must be exactly 16 bytes error"
- KB#0106 Resolve a "different operating system" error when installing the Puppet Enterprise 2017.1.1 agent RPM on AIX 7.2
- KB#0107 Migrate to a monolithic installation of Puppet Enterprise 2018.1.0 to 2018.1.7 or 2019.0.0 to 2019.0.2
- KB#0108 Remove the Puppet PC1 repository to resolve an agent installation failing with error 22 for Puppet Enterprise 2016.x - 2017.1.x
- KB#0109 Configure compile masters for a multi-region infrastructure for Puppet Enterprise 2016.x to 2017.1.x and 2017.3.x to 2019.0.x
- KB#0110 Setting the console password fails in the AWS marketplace Puppet Enterprise 2017.1.1 image with "invalid byte sequence in US-ASCII"
- KB#0111 Workaround for PostgreSQL CPU usage increase after upgrading to Puppet Enterprise 2016.5.x
- KB#0113 Puppet Enterprise 2016.5.x upgrade fails with a "Failed to apply catalog" error
- KB#0101 Should I upgrade to the latest version of Puppet Enterprise for new features or stay with Puppet Enterprise 2018.1.x?
- KB#0114 "OpenSSL::X509::StoreError" during installation of Puppet Enterprise 2016.4.x - 2017.1.x
- KB#0115 Puppet Enterprise 2016.4.2 to 2017.2.x upgrade with Hiera data in non-production environments
- KB#0116 Resolve a "libfactor was not found" error when installing Puppet Enterprise agent in PE 2016.1.x and earlier
- KB#0117 Resolve an issue with a /tmp directory mounted as noexec when installing PE 2016.1.x
- KB#0118 Resolve an " \"etag \" does not exist" error when upgrading to Puppet Enterprise 2016.2.0
- KB#0119 Upgrade to 2016.2 completed with no errors, but Puppet run after upgrade fails, and PE services are down
- KB#0120 Upgrading to PE 2016.2
- KB#0121 Resolving an evaluation error when installing Puppet Enterprise 2016.2.0
- KB#0122 Resolving a "classification conflict" error after upgrading to Puppet Enterprise 2016.2.0