These are the known issues for configuration and maintenance in this release.
Restoring to a former agent node with a signed certificate in the master's
ssl/ca/signed directory fails
If you attempt to back up data to a former agent node whose node certificate still exists in the
/etc/puppetlabs/puppet/ssl/ca/signed directory that is part of the backup tarball, the restore fails when it attempts to regenerate a new certificate for the master.
pe-rbac database fails with the
puppet-backup restore command
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.
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