[Satellite 6] RHEL 5 client systems puppet agent fails to start / register correctly with "Exiting; no certificate found and wait for cert is disabled" "Error: unknown message digest algorithm"

Solution Verified - Updated -

Issue

  • When using a Satellite 6 server deployed on RHEL 7 OS, attempts to register the puppet agent on a RHEL5 system with the puppet master on Satellite 6 (either in kickstart %post install or via the command line at a later time) the puppet agent will fail to start and register correctly, you are left with:
# /usr/bin/puppet agent -v --config /etc/puppet/puppet.conf -o --tags no_such_tag --server <serverfqdn> --no-daemonize
Exiting; no certificate found and waitforcert is disabled

On the Puppet master if you try and sign it manually you get:

# puppet cert sign --digest SHA1 <serverfqdn>
Error: unknown message digest algorithm

Environment

  • Red Hat Satellite 6 running on Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 5 client system

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content