Configuration and maintenance known issues

These are the known issues for configuration and maintenance in this release.

puppet infrastructure tune fails with multi-environment environmentpath

The puppet infrastructure tune command fails if environmentpath (in your puppet.conf file) is set to multiple environments. To avoid the failure, comment out this setting before running this command. For details about the environmentpath setting, refer to environmentpath in the open source Puppet documentation.

Restarting or running Puppet on infrastructure nodes can trigger an illegal reflective access operation warning

When restarting PE services or performing agent runs on infrastructure nodes, you might see this warning in the command-line output or logs: Illegal reflective access operation ... All illegal access operations will be denied in a future release

These warnings are internal to PE service components and have no impact on their functionality. You can safely disregard them.

JRuby instance flushing may cause a memory leak

JRuby instance flushing may cause a memory leak for many, if not all, of our users. We recommend that users who have set their max-requests-per-instance settings for JRuby pools to custom, non-zero values to either move them to be unmanaged i.e. accept the default value or explicitly set the default value to 0 (the new default). Please do not manually flush the JRuby pool via the HTTP API.

Puppet backup create/restore fails when puppet_enterprise::puppetdb_port is changed

In PE 2023.7.7-2023.8.5 and 2025.0-2025.5, when the puppet_enterprise::puppetdb_port is changed to something other than 8081, backup create/restore fails. This issue will be fixed in PE 2023.8.6 and 2025.6.0.

Infra Assistant database encryption keys are included in the archive created through Puppet backup

In PE 2025.4.0 and 2025.5, the encryption key used for encrypting content in the Infra Assistant database was not excluded from the files gathered by Puppet backup. This issue will be fixed in PE 2025.6.

If you’ve created a backup archive, we recommend rotating the encryption key:

1. Move or delete the keys.json file at: /etc/puppetlabs/infra-assistant/conf.d/secrets.

2. Restart the pe-infra-assistant service. The pe-infra-assistant service will generate a new key at startup.

3. Using the PE console or the Infra Assistant API, replace the previous AI provider settings with new settings including a new access token generated by your AI provider.