Feature #31509
Allow changing some Foreman Proxy and Apache hostnames on Katello-based certificates
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
No
Description
The Katello certificates default to using the FQDN but it's possible to run the installer with --certs-node-fqdn to change the hostname. However, this is not respected for the Foreman Proxy and Apache certificates.
Related issues
Associated revisions
History
#1
Updated by Ewoud Kohl van Wijngaarden over 2 years ago
Updated by - Blocks Feature #26103: ensure the hostname of the machine didn't change between installer runs added
#2
Updated by The Foreman Bot over 2 years ago
Updated by - Assignee set to Ewoud Kohl van Wijngaarden
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/307 added
#3
Updated by The Foreman Bot over 2 years ago
- Fixed in Releases 2.4.0 added
#4
Updated by Ewoud Kohl van Wijngaarden over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman_proxy_content|537a2a61be86d6c6b0e9c2307c542c89ed59a36b.
Fixes #31509 - Allow changing node FQDN
The Katello certificates default to using the FQDN. This is done in the
certs class via the node_fqdn parameter. The specific classes have a
parameter named hostname which defaults to $certs::node_fqdn.
Prior to this patch, those hostnames were hardcoded to the FQDN fact
which made it impossible to decouple the system hostname from the
service name. With this change, it is possible to do so.
The Puppet certificate is matched to the Foreman Proxy since these in
fact must have the same name. Otherwise Foreman authentication will
fail. That is because the Puppet scripts "authenticate" via the Smart
Proxy registration by using the same Common Name on the certificate.