Continuous Delivery for PE known issues

These are the known issues for the Continuous Delivery for Puppet Enterprise (PE) 5.x release series.

Creating or editing a pipeline with deployments causes the deployments to stop running

Using the Continuous Delivery for PE 4.29.0 or 5.3.0 web UI to create or edit a pipeline that contains a deployment causes the pipeline to stop running its deployments. Jobs and Impact Analyses continue to work and pipelines continue to run, but deployments are skipped. This does not affect pipelines that do not contain deployments, pipelines managed with code, or versions of Continuous Delivery for PE prior to, or later than, 4.29.0 or 5.3.0.

Optional environment variables are not being passed to Docker containers

For Continuous Delivery for Puppet Enterprise (PE) 5.1.2 and earlier, on the Jobs page, environment variables that are added to the Optional configuration section are unavailable in the Docker container. To work around this issue, add a secret to the job with the environment data you want to use. You can then reference the variable it creates to access your data.

A Puppet Enterprise (2023.4 or later) module is not compatible with Ruby 3.2

A module included with Puppet Enterprise 2023.4 or later is not compatible with Ruby 3.2. While this does not affect Puppet Enterprise users, it can affect users integrating Continuous Delivery for Puppet Enterprise (PE) 5.1.2 and earlier with these versions of PE. If you are integrating Continuous Delivery for PE 5.1.2 and earlier with Puppet Enterprise 2023.4 or later, install a version of the module compatible with newer Ruby versions using the following command:

puppet module upgrade puppetlabs-cd4pe_jobs

Continuous Delivery for Puppet Enterprise (PE) fails when used with Puppet 8 (Puppet Enterprise 2023.4 or later)

Puppet 8 (included with Puppet Enterprise 2023.4 or later) has removed legacy facts by default. Continuous Delivery for PE 5.1.2 and earlier relies on the legacy fact operatingsystem in order to develop a list of systems that are available to be used as job hardware. If you are running Continuous Delivery for PE 5.x with Puppet Enterprise 2023.4 or later, you need to add the following to puppet.conf:

include_legacy_facts=true

Continuous Delivery for Puppet Enterprise (PE) fails to restart after rebooting host

If you are running Continuous Delivery for Puppet Enterprise (PE) 5.1.2 and earlier with the Podman runtime, Continuous Delivery for Puppet Enterprise (PE) may not restart after a host reboot. Run the following (using puppetlabs-cd4peadm) to get Continuous Delivery for Puppet Enterprise (PE) back up:

bolt plan run cd4peadm::ctl action=stop
bolt command run "rm /etc/puppetlabs/cd4pe/*.ip.txt" --targets cd4pe-5-host
bolt plan run cd4peadm::ctl action=start

Continuous Delivery for Puppet Enterprise (PE) fails to install on localhost

Users installing Continuous Delivery for Puppet Enterprise (PE) 5.1.2 and earlier using Bolt's local transport may encounter an error if /etc/puppetlabs has not been created. To work around this issue, create the directory /etc/puppetlabs before installing.

Jobs fail in 5.x due to improperly configured CA certificate

Users running Continuous Delivery for Puppet Enterprise (PE) 5.1.2 and earlier may encounter an SSL error with the message certificate verify failed (certificate signature failure) when running jobs in 5.x. To work around this, restart the UI container on the Continuous Delivery for Puppet Enterprise (PE) host.