Consolidated Troubleshooting Article for Red Hat Satellite 6.x Puppet Issues
Updated
Issues
Starting Puppet server
- Puppet server fails to start on Satellite/Capsule 6.x with
NameError: cannot load Java class org.jruby.ext.psych.PsychLibrarydue tofapolicydservice being enabled - Puppet server fails to start on Red Hat Satellite 6.x with
NameError: cannot load Java class org.jruby.ext.psych.PsychLibrarydue to Puppet being disabled - Puppetserver service fails to start with error (UnsupportedClassVersionError) at java.lang.ClassLoader/defineClass1 on Red Hat Satellite 6
- Puppetserver service fails to start with error "Permission denied - /var/log/puppetlabs/puppetserver" in Red Hat Satellite 6
Other Issues
- Why re-registering a host or a capsule to Satellite fails with error "Validation failed: Puppet Capsule does not have the Puppet feature, Puppet ca Capsule does not have the Puppet CA feature (HTTP error code 422: Unprocessable Entity)"?
- [satellite6] puppet agent too slow or timeout
- Unable to sign the SSL certificate for the puppet client in the satellite webUI
- How to resolve /opt/puppetlabs/bin/puppetserver ca setup' returned 1 instead of one of [0] ?
- Empty stats for Puppet runs for hosts registered to Red Hat Satellite Capsule
- Puppet server classes cache is disabled, classes retrieval can be slow.
- Running Satellite OpenScap and puppet agent fails with '/usr/bin/foreman_scap_client: No such file or directory' error message
- Puppet Server Error: Failed to find HOSTNAME via exec: Execution of '/etc/puppetlabs/puppet/node.rb HOSTNAME' returned 1
- Puppet fails with Error 500 on SERVER: Server Error: Failed when searching for node client.example.com
- Puppet run on the Satellite client shows the
Debug: Failed to load library msgpack for feature msgpackdebug message. - Getting error "Warning: Error 400 on SERVER: Failed to find xxx via exec: Execution of '/etc/puppet/node.rb xxx ' returned 1" when running puppet agent command
- Puppet run fails on the Client with error Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Unknown function: 'upcase'.
- Puppet client connected to Satellite 6 reports Foreman_scap_client error
- Puppet run fails on system registered to Red Hat Satellite 6 with error: could not find class stdlib for client.example.com.
- Error persists even after removing puppet class from hostgroup
- [Satellite6] Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Type-Name, Could not autoload puppet/type
- Puppet run on clients registered with Red Hat Satellite 6 fails with Evaluation Error: Error while evaluating a Function Call, 'new' Value of type Undef cannot be converted to Integer
- Unable to run puppet agent --test in client machine - Red Hat Satellite
- puppet agent -t Error: The certificate retrieved from the master does not match the agent's private key
- Satellite 6 puppet "Error 400 on SERVER: Could not find class foreman_scap_client"
- TEST Satellite: After migrating to v6.4 I see PUPPET 'stdlib' issues
- Puppet on client registered with Red Hat Satellite 6 fails with "Could not retrieve catalog from remote server: SSL_CTX_use_PrivateKey: key values mismatch"
- The host configuration chart shows 100% on dashboard for Red Hat Satellite 6 even if few hosts are out of sync.
- On Red Hat Satellite 6 Dashboard, Host Configuration Chart shows Out of Sync for hosts that no longer run puppet agent
- Why can't I see any Puppet reports from the hosts in my Satellite 6?
- [Satellite6] Puppet reports view show the maximum event number displayed is 63 regardless of how many more issues are 'Pending/Applied'.
- Host status shows 'Out of Sync' on Red Hat Satellite 6 Web-ui
- Puppet 4.x and later stores the Puppet certificates under /var/lib/puppet/ssl rather than /etc/puppetlabs/puppet/ssl on running 'puppet agent -t'
- Puppet agent fails with "Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `exists?' for nil:NilClass"
- Upgrading Red Hat Satellite server fails with error Procedures::Installer::Upgrade: Could not get default values
- Running "satellite-maintain packages update gofer" on Red Hat Capsule server 6.x results in: Procedures::Installer::Upgrade: Could not get default values, check log file at /var/log/foreman-installer/capsule.log for more information.
- Red Hat Satellite 6 throws the exception: "ERF12-5356 [ProxyAPI::ProxyException]: Unable to get PuppetCA certificates"
- Impossible to re-enable puppet plugin if it was disabled and removed using -f or --remove-all-data option
How To
- How to completely remove puppet functionality from Satellite 6.11?
- Satellite 6: How to extract client system information / facts without installing puppet agent package?
- How to regenerate the Puppet CA and Puppet Client certificates for Red Hat Satellite?
- [Satellite 6] Purging Puppet reports stored on a Satellite 6.x server
- [Satellite 6] How to make queries for failed Puppet reports to Satellite from API?
- Satellite 6 : How to restore Satellite's and client Puppet SSL certificates after they were revoked by a mistake.
Q & A
- What will happen to Puppet content on Red Hat Satellite server after upgrade to Satellite 6.10?
- Is it possible to use 'puppet module install module-name' command with puppet repositories hosted on Satellite 6 ?
SBR
Product(s)
Components
Article Type