Problem:
Expected outcome: certificate issuer information, SSL certificate paths, and Smart Proxy/Puppet configuration files expected to use new server hostname
Foreman and Proxy versions: 3.12 and 3.12
Foreman and Proxy plugin versions:
Distribution and version: RHEL-9
Other relevant data:
-
Foreman/Katello Server
-
Source OS: RHEL 8
-
Target OS: RHEL 9
-
Migration Method: Backup and Restore
-
Hostname Changed: Yes
Issue Description
We migrated our Foreman/Katello server from an existing RHEL 8 server to a new RHEL 9 server. The migration completed successfully, and all Foreman/Katello services, repositories, content views, and managed hosts appear to be functioning normally.
However, during post-migration validation, we discovered that several certificates and configuration files still contain references to the old Foreman hostname.
The new server is operational using the new hostname, but certificate issuer information, SSL certificate paths, and Smart Proxy/Puppet configuration files continue to reference the old hostname.
grep -R old-foreman-server /etc/foreman*
/etc/foreman/client_cert.pem: Issuer: C=US, ST=North Carolina, L=Raleigh, O=Katello, OU=SomeOrgUnit, CN=old-foreman-server
/etc/foreman/client_cert.pem: DirName:/C=US/ST=North Carolina/L=Raleigh/O=Katello/OU=SomeOrgUnit/CN=old-foreman-server
/etc/foreman-installer/scenarios.d/katello-answers.yaml: ssl_certificate: “/etc/puppetlabs/puppet/ssl/certs/old-foreman-server.pem”
/etc/foreman-installer/scenarios.d/katello-answers.yaml: ssl_private_key: “/etc/puppetlabs/puppet/ssl/private_keys/old-foreman-server.pem”
/etc/foreman-installer/scenarios.d/katello-answers.yaml: puppet_ssl_cert: “/etc/puppetlabs/puppet/ssl/certs/old-foreman-server.pem”
/etc/foreman-installer/scenarios.d/katello-answers.yaml: puppet_ssl_key: “/etc/puppetlabs/puppet/ssl/private_keys/old-foreman-server.pem”
/etc/foreman-installer/scenarios.d/katello-answers.yaml: dns_tsig_principal: foremanproxy/old-foreman-server@domain.com
/etc/foreman-proxy/ssl_cert.pem: Issuer: C=US, ST=North Carolina, L=Raleigh, O=Katello, OU=SomeOrgUnit, CN=old-foreman-server
/etc/foreman-proxy/ssl_cert.pem: DirName:/C=US/ST=North Carolina/L=Raleigh/O=Katello/OU=SomeOrgUnit/CN=old-foreman-server
/etc/foreman-proxy/settings.yml_bkp-30062025: - old-foreman-server
/etc/foreman-proxy/settings.yml_bkp-30062025::foreman_url: https://old-foreman-server
/etc/foreman-proxy/foreman_ssl_cert.pem: Issuer: C=US, ST=North Carolina, L=Raleigh, O=Katello, OU=SomeOrgUnit, CN=old-foreman-server
/etc/foreman-proxy/foreman_ssl_cert.pem: DirName:/C=US/ST=North Carolina/L=Raleigh/O=Katello/OU=SomeOrgUnit/CN=old-foreman-server
/etc/foreman-proxy/settings.d/dns_nsupdate_gss.yml::dns_tsig_principal: foremanproxy/old-foreman-server@domain.com
/etc/foreman-proxy/settings.d/puppet_proxy_puppet_api.yml::puppet_ssl_cert: /etc/puppetlabs/puppet/ssl/certs/old-foreman-server.pem
/etc/foreman-proxy/settings.d/puppet_proxy_puppet_api.yml::puppet_ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/old-foreman-server.pem
/etc/foreman-proxy/settings.d/puppetca_http_api.yml::puppet_ssl_cert: /etc/puppetlabs/puppet/ssl/certs/old-foreman-server.pem
/etc/foreman-proxy/settings.d/puppetca_http_api.yml::puppet_ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/old-foreman-server.pem