These are the known issues in PE 2019.1.
Installation and upgrade known issues
These are the known issues for installation and upgrade in this release.
Missing package dependencies for SUSE Linux Enterprise Server agent nodes
On agent nodes running SUSE Linux Enterprise Server 15, the
libyaml-cpp package and operating system packages
libboost_ are no longer bundled with
Puppet agent, and might not be included in the
operating system. See SUSE Linux Enterprise Server dependencies for the full list of
required packages. The
libyaml-cpp package is in the
Desktop Applications SUSE Linux Enterprise Server packaging module, and
libboost packages are in the Basesystem module.
If you encounter issues when installing Puppet agent on SUSE Linux Enterprise Server 15 nodes, use
package-search or the SUSE Linux Enterprise Server Customer
Center packages list at https://scc.suse.com/packages to locate the packages and
instructions on how to install them manually.
Web-based installation requires a second Puppet run to fully install PE services
Web-based installation includes a single, initial Puppet run, but a second Puppet run is required in order
services.conf. Until a second Puppet run completes, the Puppet service status in the console reports that one
or more services isn't accepting requests.
Console output is shown when installing in quiet mode
When running the installer in
text mode, adding the
-q option does not successfully activate quiet mode, and the
installation process is logged in the console.
Installer can fail due to SSL errors with AWS
In some cases, master platforms receive SSL errors when attempting to connect to s3.amazonaws.com, and so are unable retrieve agent packages needed for installation. Updating the CA cert bundle on the master platform usually resolves the problem. To update the bundle, run the following commands:
rm /etc/ssl/certs/ca-bundle.crt yum reinstall ca-certificates
After you update the CA bundle, run the installer again.
Configuration and maintenance known issues
These are the known issues for configuration and maintenance in this release.
recover_configuration misreports success if specified environment
If you specify an invalid environment
recover_configuration, the system erroneously reports that the
environment's configuration was saved.
pe-rbac database fails
When restoring the
pe-rbac database, the
restore process exits with errors about a duplicate operator family,
- Log into your existing PostgreSQL instance:
sudo su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql pe-rbac"
- Issue these commands:
ALTER EXTENSION citext ADD operator family citext_ops using btree; ALTER EXTENSION citext ADD operator family citext_ops using hash;
- Exit the PostgreSQL shell and re-run the backup utility.
if gems are missing from the master's agent environment
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, install missing or incorrectly versioned gems on the master's agent environment. To
find which gems are causing the error, check the backup logs for gem incompatibility
issues with the error message. PE creates backup logs
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
Orchestration services known issues
These are the known issues for the orchestration services in this release.
Orchestrator fails when rerunning tasks on agentless nodes
When you rerun tasks from the Job details page, target nodes that do not have an agent installed are miscategorized as PuppetDB nodes. This causes the orchestrator to fail on those nodes.
Code management known issues
These are the known issues for Code Manager, r10k, and file sync in this release.
Default SSH URL with TFS fails with Rugged error
the default SSH URL with Microsoft Team Foundation Server
(TFS) with the
rugged provider causes an error of
"unable to determine current branches for Git source." This is
rugged provider expects an
@ symbol in
the URL format.
To work around this error,
ssh:// in the default URL with
updates may cause errors with
has disabled TLSv1, TLSv1.1 and some SSH cipher suites, which may
cause automation using older crypto libraries to start failing. If
you are using Code Manager or r10k with the
provider enabled, you might see negotiation errors on some platforms
when fetching modules from the Forge. To resolve these errors,
switch your configuration to use the
rugged provider, or
shellgit by updating your OS package.
Timeouts when using
--wait with large
deployments or geographically dispersed compilers
--wait flag deploys code to all compilers before returning results,
some deployments with a large node count or compilers spread across
a large geographic area might experience a timeout. Work around this
issue by adjusting the
r10k with the Rugged provider can develop a bloated cache
If you use the
rugged provider for r10k, repository pruning is not
supported. As a result, if you use many short-lived branches, over
time the local r10k cache can become
bloated and take up significant disk space.
If you encounter this issue, run
git-gc periodically on any cached repo that is
using a large amount of disk space in the cachedir. Alternatively,
shellgit provider, which
automatically garbage collects the repos according to the normal Git
Code Manager and r10k do not identify the default branch for module repositories
When you use Code Manager or r10k to deploy modules from a
Git source, the default branch of the source repository is always
assumed to be master. If the module repository uses a default branch
that is not master, an error
occurs. To work around this issue, specify the default branch with
ref: key in
After an error during the initial run of file sync, Puppet Server won't start
The first time you run Code Manager and file sync on a master, an error can occur that prevents Puppet Server from starting. To work around this issue:
- Stop the
- Locate the data-dir variable in
- Remove the directory.
- Start the
Repeat these steps on each master exhibiting the same symptoms, including any compilers.
Puppet Server crashes if file sync can't write to the live code directory
If the live code directory contains content that file sync didn’t expect to find there (for example, someone has made changes directly to the live code directory), Puppet Server crashes.
The following error appears in
2016-05-05 11:57:06,042 ERROR [clojure-agent-send-off-pool-0] [p.e.s.f.file-sync-client-core] Fatal error during file sync, requesting shutdown. org.eclipse.jgit.api.errors.JGitInternalException: Could not delete file /etc/puppetlabs/code/environments/development at org.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:138) ~[puppet-server-release.jar:na]
To recover from this error:
- Delete the environments in code dir:
find /etc/puppetlabs/code -mindepth 1 -delete
- Start the
puppet resource service pe-puppetserver ensure=running
- Trigger a Code Manager run by your usual method.
Internationalization known issues
These are the known issues for internationalization and UTF-8 support in this release.
Names for environments, variables, classes, resource types, modules, parameters, and tags in the Puppet language.
File names, which can generate errors when referenced as a
sourcein a file resource or concat fragment.
namevarfor certain resource types, on certain operating systems. For example, the user and group resources on RHEL and CentOS may contain only ASCII characters in
The console password.
Ruby can corrupt the
path fact and
environment variable on Windows
There is a bug in Ruby that can corrupt the environment variable names and values. This bug causes corruption for only some codepages. This bug might be triggered when environment names or values contain UTF-8 characters that can't be translated to the current codepage.
The same bug can cause the
path fact to be cached in a corrupt state.