Continuous Delivery for Puppet Enterprise
- Update the pe-r10k package in Puppet Enterprise 2019.8.7 and 2021.2 if you are using Continuous Delivery for PE impact analysis
- After upgrading Continuous Delivery for Puppet Enterprise you get an “Insufficient cpu” error
- Resolve an “{”errors”:[“invalid secret id”]}” error message in Continuous Delivery for Puppet Enterprise
- When your Kubernetes cluster is offline in Continuous Delivery for Puppet Enterprise, you can’t generate a support bundle from the command line
- Code deployment in Continuous Delivery for Puppet Enterprise fails with an “Unable to connect to https://forgeapi.puppetlabs.com” error
- Change the backup timeout parameter when a snapshot fails in Continuous Delivery for Puppet Enterprise
- Certificates expire in Puppet Application Manager version 1.62.0 in Continuous Delivery for Puppet Enterprise
- Rebuild Kubernetes IPtables rules in Continuous Delivery for Puppet Enterprise
- Get Puppet Application Manager and Continuous Delivery for Puppet Enterprise version and troubleshooting information
- When upgrading Puppet Application Manager you get an “error when evicting pod” error in Continuous Delivery for Puppet Enterprise
- You can’t create Puppet Application Manager snapshots for your Continuous Delivery for Puppet Enterprise deployment
- Delete an incomplete backup in Puppet Application Manager in Continuous Delivery for Puppet Enterprise
- When trying to connect to A PAM Kubernetes cluster (“kubectl…”) you get a “The connection to the server localhost:8080 was refused” error in Continuous Delivery for Puppet Enterprise
- Branch names with non-word characters (including dots) work in Puppet Enterprise but do not work in Continuous Delivery for Puppet Enterprise
- Performance issues and many calls to “/puppet/v4/catalog” after enabling impact analysis in Continuous Delivery for Puppet Enterprise
- Unblock Kubernetes when creating new pods in Continuous Delivery for Puppet Enterprise
- Resolve a “certificate verify failed (certificate has expired)” error in Continuous Delivery for Puppet Enterprise
- Resolve a “java.lang.IllegalArgumentException: URI is not absolute” error in Continuous Delivery for Puppet Enterprise
- When upgrading Continuous Delivery for Puppet Enterprise and Puppet Application Manager, you lose connectivity to your cluster
- Reset the Puppet Application Manager password in Continuous Delivery for Puppet Enterprise
- Pipelines-as-code issues in Continuous Delivery for Puppet Enterprise 3.0.0 to 4.15.1
- Onceover fails with a “Error during concurrent deploy of a module” in Continuous Delivery for Puppet Enterprise
- Recommended reading: Running Continuous Delivery for Puppet Enterprise Impact Analysis at scale
- Resolve a “Permission denied” error in Continuous Delivery for Puppet Enterprise when SELinux is set to “enforced”
- Build a custom installer for Puppet Application Manager and use it to migrate to a new cluster for Continuous Delivery for Puppet Enterprise
- Fix a mismatched kurl-registry-ip for an incomplete offline Puppet Application Manager cluster migration in Continuous Delivery for Puppet Enterprise
- Migrate to a supported architecture of Puppet Application Manager for Continuous Delivery for Puppet Enterprise
- Uninstall Continuous Delivery for Puppet Enterprise version 4.x without uninstalling Puppet Application Manager
- Resolve a "Job cd4pe-migrate-object-store is invalid" error when upgrading or re-deploying Continuous Delivery for Puppet Enterprise
- “Error from server (Invalid): error when applying patch” after upgrading Continuous Delivery for Puppet Enterprise