Puppet errors after upgrade from 1.22.0 to 1.22.1

Support
1

Problem:
I upgraded my Foreman + Katello installation from 1.22.0 to 1.22.1 using Yum (did not change repos or anything like that, just a plain yum update).

It seemed to go fine but I’m now seeing this error when rebuilding a host.

01-tiny
01-tiny700×458 132 KB

Failed to enable fmtest4.example.com for installation: [“Enable PuppetCA autosigning for fmtest4.example.com task failed with the following error: ERF12-0104 [ProxyAPI::ProxyException]: Unable to set PuppetCA autosign for fmtest4.example.com ([RestClient::NotFound]: 404 Not Found) for proxy https://hardhat.example.com:9090/puppet/ca”, “Failed to perform rollback on Disable PuppetCA autosigning for fmtest4.example.com - ERF12-0104 [ProxyAPI::ProxyException]: Unable to set PuppetCA autosign for fmtest4.example.com ([RestClient::NotFound]: 404 Not Found) for proxy https://hardhat.example.com:9090/puppet/ca”]

Please note I’m using a Puppet5 master, not the suggested Puppet6.

Expected outcome:
Rebuild should work cleanly.

Foreman and Proxy versions:
Foreman: 1.22.1

Foreman and Proxy plugin versions:
Katello: 3.12.3
foreman-tasks: 0.15.11

Other relevant data:
Haven’t had a chance to grab proper logs yet, will try to soon.

2

Going into Infrastructure -> Smart Proxies, it looks like the Puppet features are in a failed state:

Failed features

Puppetca puppet cert Puppetca hostname whitelisting Puppet CA

Digging further I’ve got this error message - Disabling all modules in the group [‘puppetca_puppet_cert’, ‘puppetca_hostname_whitelisting’, ‘puppetca’] due to a failure in one of them: Parameter ‘ssldir’ is expected to have a non-empty value

3

Per Foreman Smart Proxy failed features Puppet CA hostname whitelisting & Puppet CA I had NOT properly followed the instructions. This was resolved by re-running foreman-installer.