Frankly I have no idea what’s wrong…
However I’ve done the following on the smart proxy:
- Moved away everything in /root/ssl-build/
- yum remove improdforemansmartpxy01.iom.local-qpid-router-server improdforemansmartpxy01.iom.local-apache improdforemansmartpxy01.iom.local-puppet-client improdforemansmartpxy01.iom.local-foreman-proxy improdforemansmartpxy01.iom.local-qpid-router-client improdforemansmartpxy01.iom.local-foreman-proxy-client
- Instead of using the generated certs tar as described in the upgrade guide I used the certs tar created when I initially set up the smart proxy (lucky I still had that around!)
# foreman-installer \
--scenario foreman-proxy-content \
--certs-tar-file "/root/foremansmartpxy.fishy.com-certs.tar"\
--foreman-proxy-register-in-foreman "true"\
--foreman-proxy-foreman-base-url "https://foremankatello.fishy.com"\
--foreman-proxy-trusted-hosts "foremankatello.fishy.com"\
--foreman-proxy-trusted-hosts "foremansmartpxy.fishy.com"\
--foreman-proxy-oauth-consumer-key "XXXXXXXXXXXXXXXXXX"\
--foreman-proxy-oauth-consumer-secret "YYYYYYYYYYYYYYYYYYYY"\
--puppet-server-foreman-url "https://foremankatello.fishy.com"
1st run of the installer complained about:
foremansmartpxy.fishy.com-foreman-proxy
foremansmartpxy.fishy.com-local-apache
not being found which is completely wrong as they are in the tar file…
2nd run of the installer (exact same command as above) did not complain yet produced errors:
2021-06-28 09:23:35 [NOTICE] [configure] 1750 configuration steps out of 1866 steps complete.
2021-06-28 09:23:40 [ERROR ] [configure] Proxy foremansmartpxy.fishy.com has failed to load one or more features (Discovery), check /var/log/foreman-proxy/proxy.log for configuration errors
2021-06-28 09:23:40 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foremansmartpxy.fishy.com]/features: change from ["Ansible", "Container_Gateway", "DHCP", "Dynflow", "HTTPBoot", "Logs", "Openscap", "Pulpcore", "Puppet", "Puppet CA", "Registration", "SSH", "TFTP", "Templates"] to ["Ansible", "Container_Gateway", "DHCP", "Discovery", "Dynflow", "HTTPBoot", "Logs", "Openscap", "Pulpcore", "Puppet", "Puppet CA", "Registration", "SSH", "TFTP", "Templates"] failed: Proxy foremansmartpxy.fishy.com has failed to load one or more features (Discovery), check /var/log/foreman-proxy/proxy.log for configuration errors
2021-06-28 09:23:42 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foremansmartpxy.fishy.com]: Failed to call refresh: Proxy foremansmartpxy.fishy.com has failed to load one or more features (Discovery), check /var/log/foreman-proxy/proxy.log for configuration errors
2021-06-28 09:23:42 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foremansmartpxy.fishy.com]: Proxy foremansmartpxy.fishy.com has failed to load one or more features (Discovery), check /var/log/foreman-proxy/proxy.log for configuration errors
2021-06-28 09:23:44 [NOTICE] [configure] System configuration has finished.
There were errors detected during install.
Please address the errors and re-run the installer to ensure the system is properly configured.
Failing to do so is likely to result in broken functionality.
The full log is at /var/log/foreman-installer/foreman-proxy-content.log
No useful information in /var/log/foreman-proxy/proxy.log or /var/log/foreman-installer/foreman-proxy-content.log
Yet (let’s call it a Monday morning miracle!) the Smart Proxy shows all green in the Foreman/Katello server UI and I synch’ed my views (completed). I went to a VM registered via the smart proxy and ran a yum clean all ; yum update and it picked up everything new happily including new GPG keys so from that point of view it seems alright.
I’m somewhat happy it works again but my confidence in the whole process is somewhat low…
- Always fails at “1750 configuration steps out of 1866 steps complete” so has something not been completed?
- Certs regeneration from main Foreman/Katello server on 2.5.1/4.1 seems to create something incorrect…
I’m happy to provide more info if I’m directed to get to the bottom at that problem.
I’m going to have to create a few more Smart Proxies in different Geo locations and if the cert generation creates something incorrect for a new smart proxy FQDN it’s not going to be pleasant 
