PE Services and Puppet Core Known Issues

A newer version is available; see the version menu above for details.

As we discover them, this page will be updated with known issues related to PE services and the Puppet core in Puppet Enterprise 2015.2 releases. Fixed issues will be removed from this page and noted in the Bug Fixes section of the release notes. If you find new problems yourself, please file bugs in our issue tracker.

parser=future Setting in environment.conf Not Valid in PE 2015.2

If you enabled the Puppet 4 language parser in PE 3.8.x by setting parser=future in any environment.conf files, you’ll see warning messages during your upgrade, as this setting is no longer valid. After you upgrade, remove this setting from any environment.conf files.

Empty Stings in Hiera Overrides and Puppet Enterprise Class Variables May Cause Failures in Catalog Compilations

Do not use empty strings in Hiera overrides or in the variables in the Puppet Enterprise class (via changes in the console). Some arguments, if set to an empty string, may cause Puppet catalog compilations to fail.

Remove enable_future_parser Parameter After Upgrading

If you enabled the Puppet 4 language parser in PE 3.8 via the console, Hiera, or a third-party classification tool, after upgrading you must use the console to remove the enable_future_parser paramater from the puppet_enterprise::profile::master class, as this parameter is deprecated.

/opt/staging/ is No Longer Used

In PE 2015.2, the /opt/staging/ directory is no longer used. Because users may have used either the puppetlabs-pe_staging or nanliu-staging modules, we did not delete the directory. If you are not using the directory, it is safe to delete it.

Change to lsbmajdistrelease Fact Affects Some Manifests

In Facter 2.2.0, the lsbmajdistrelease fact changed its value from the first two numbers to the full two-number.two-number version on Ubuntu systems. This might break manifests that were based on the previous behavior. For example, this fact changed from: 12 to 12.04.

This change affects Ubuntu and Amazon Linux. See the Facter documentation for more information

Change allow_no_actionpolicy Parameter to Enforce MCollective Action Policies

The MCollective ActionPolicy plugin is installed by default in PE. Within the configuration of MCollective, there is a setting that can be used to enforce the use of this ActionPolicy. By default this setting (plugin.actionpolicy.allow_unconfigured) is hardcoded to 1. Unfortunately this prevents you from enforcing the use of configured Action Policies.

To change this setting, use the PE console to edit the value of the allow_no_actionpolicy parameter of the puppet_enterprise::profile::mcollective::agent class located in the PE MCollective node group. To allow ActionPolicy, enter "0". (Be sure to use quote marks, as Puppet expects a string for this value.)

Enabling NIO and Stomp for ActiveMQ Performance Improvements will Introduce Security Issues

Enabling ActiveMQ’s use of the NIO protocol in PE can improve the speed at which orchestration messages are sent across your deployment. However, when this is enabled, any parameters that you define for which SSL protocols to use will be ignored, and SSL version 3 will be enabled. Apache has fixed this bug, but they have not yet released a version of ActiveMQ that contains the fix. For more information, refer to their public ticket.

Considering security over performance, PE 2015.2 ships with NIO disabled. You can enable it with the following procedure:

  1. From the console, click Classification in the navigation bar.
  2. From the Classification page, click the PE ActiveMQ Broker group.
  3. Click the Classes tab, and find puppet_enterprise::profile::amq::broker in the list of classes.
  4. From the parameter drop-down menu, choose openwire_protocol, and in the value field add nio+ssl.
  5. Click Add parameter.
  6. From the parameter drop-down menu, choose stomp_protocol, and in the value field add stomp+nio+ssl.
  7. Click Add parameter.
  8. Click Commit 2 changes.

site.pp Must Be Duplicated for Each Environment

You can no longer have a universal or global site.pp. The default main filebucket is configured as a resource default in site.pp. This means that site.pp must be duplicated for each environment. See the Puppet environments documentation for more information.

puppet module list --tree Shows Incorrect Dependencies After Uninstalling Modules

If you uninstall a module with puppet module uninstall <module name> and then run puppet module list --tree, you will get a tree that does not accurately reflect module dependencies.

The Puppet Module Tool (PMT) Does Not Support Solaris 10, AIX, or RHEL 4

When attempting to use the PMT on Solaris 10, AIX, or RHEL 4, you’ll get an error similar to the following:

	Error: Could not connect via HTTPS to
  		Unable to verify the SSL certificate
	The certificate may not be signed by a valid CA
	The CA bundle included with OpenSSL may not be valid or up to date

This error occurs because there is no CA-cert bundle on Solaris 10, AIX, or RHEL 4 to trust the Puppet Labs Forge certificate. To work around this issue, we recommend that you download directly from the Forge website and then use the Puppet module tool to install from a local tarball.

↑ Back to top