After upgrading, you should do a few more things to make Puppet easier to maintain.
Puppet 4 changed the locations of many configuration files. If you have any other systems that reuse Puppet’s SSL credentials, configuration data, or generated data, point them to the new directories.
If you back up data in directories that moved (like
/etc/puppet, whose contents are now split between
/etc/puppetlabs/code), update your backup jobs to use the new locations.
/etc/puppetdirectory on *nix systems
Avoid maintenance and configuration confusion by deleting the old
/etc/puppet directory on your *nix systems. This prevents other systems from using stale data and protects sysadmins from accidentally updating the wrong copies of files.
puppet_agentclass from nodes
puppet_agent module doesn’t affect nodes running Puppet >=4, and you can unassign it from all nodes after your entire Puppet infrastructure is upgraded.