- NEW: puppet generate types fails on the pe_java_ks module
- puppet-backup fails if gems are missing from the master's agent environment
- Restart shell after install for PE client tools subcommands
- Change to lsbmajdistrelease fact affects some manifests
- Change allow_no_actionpolicy parameter to enforce MCollective action policies
- puppet module list --tree shows incorrect dependencies after uninstalling modules
- The puppet module command does not support Solaris 10
These are the known issues for Puppet and Puppet services in this PE release.
NEW: puppet generate types fails on the pe_java_ks module
puppet generate typeson the
pe_java_ksmodule results in an error similar to:
puppet generate types >/dev/null Error: /etc/puppetlabs/code/environments/production/modules/java_ks/lib/puppet/type/java_ks.rb: title patterns that use procs are not supported. Error: /opt/puppetlabs/puppet/modules/pe_java_ks/lib/puppet/type/pe_java_ks.rb: title patterns that use procs are not supported.
puppet-backup fails if gems are missing from the master's agent environment
puppet-backup create command might fail if any gem installed on the Puppet Server isn't present on the agent environment on the master. If the gem is either absent or of a different version on the master's agent environment, you'll get the error "command
puppet infrastructure recover_configuration failed".
To fix this, you'll need to install any missing or incorrectly versioned gems on the master's agent environment.
To find which gems are causing the error, check the backup logs for any gem incompatibility issues with the error message. PE creates backup logs as a
report.txt whenever you run a
To see what gems and their versions you have installed on your Puppet Server, run the command
puppetserver gem list . To see what gems are installed in the agent environment on your master, run
Restart shell after install for PE client tools subcommands
After installing PE, the commands in the PE client tools aren't available on the PATH until you restart your shell.
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 and Amazon Linux systems. This might break manifests that were based on the previous behavior. For example, this fact changed from:
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. This default prevents you from enforcing the use of configured action policies.
To change this setting, use the 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
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 see a tree that does not accurately reflect module dependencies.
The puppet module command does not support Solaris 10
When attempting to use the
puppet module command on Solaris 10, you'll get an error like:
Error: Could not connect via HTTPS to https://forgeapi.puppetlabs.com 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 to trust the Forge certificate. To work around this issue, download directly from the Forge website and then use the
puppet module install command to install from a local tarball.