That sounds to me like your puppet agent is not properly configured, since adding --server <fqdn> seems to work. If the error actually contains 'CN=' and you just did not edit out something there, that sounds like it is missing a server in the conf.
In the kickstart preview, you should have a section for the puppet.conf, starting with cat > /etc/puppetlabs/puppet/puppet.conf << EOF.
In that config, look for the server, ca_server and cername options and check if those are correct. You should also double-check that the config on the agent host is the same.
1 Like
It works now! I just tested it a few times and the node installs the puppet repo, puppet agent, and run the puppet agent command unattended. Thank you so much for you help! I learned some very helpful troubleshooting tips from you areyus.
To recap in case this helps anyone who stumbles across this with a similar issue:
- Log into the Foreman dashboard, go to host section, click the host, go to the puppet tab, check the ENC preview to ensure parameters and classes are going to be included in the build.
- Do not regenerate certs if you can help it, as it could potentially break Foreman.
- If the node builds, but is not applying classes, review the install.post.log file in root’s home directory.
- Review the production.log.
- Physically watch the node build to see if there are any unusual messages/errors that need to be resolved.
- Check the provisioning template you are using and preview the KS commands it runs. Manually run the puppet-related commands one by one followed by the “puppet agent --test” command to ensure it pulls the catalog properly. If not, review the error and troubleshoot.
- Start fresh and delete the host, then recreate the host instead of rebuilding.
1 Like