Skip to content

Latest commit

 

History

History
84 lines (78 loc) · 4.16 KB

proc_renaming-server.adoc

File metadata and controls

84 lines (78 loc) · 4.16 KB

Renaming {ProjectServer}

The host name of {ProjectServer} is used by {ProjectServer} components, all {SmartProxyServers}, and hosts registered to it for communication. This procedure ensures that in addition to renaming {ProjectServer}, you also update all references to point to the new host name.

Warning

Renaming your {ProjectServer} host shuts down all {Project} services on that host. The services restart after the renaming is complete.
Prerequisites

  • Back up your {ProjectServer} before changing its host name. If you fail to successfully rename it, restore it from the backup. For more information, see [backing-up-{project-context}-server-and-{smart-proxy-context}_{context}].

  • Run the hostname and hostname -f commands on {ProjectServer}. If both commands do not return the FQDN of {ProjectServer}, the {project-change-hostname} script will fail to complete.

    If the hostname command returns the shortname of {ProjectServer} instead of the FQDN, use hostnamectl set-hostname My_Old_FQDN to set the old FQDN correctly before using the {project-change-hostname} script.

  • If {ProjectServer} has a custom SSL certificate installed, obtain a new certificate for the new FQDN of the host. For more information, see {InstallingServerDocURL}configuring-satellite-custom-server-certificate_{project-context}[Configuring {ProjectServer} with a Custom SSL Certificate] in {InstallingServerDocTitle}.

Procedure

  1. On {ProjectServer}, run the {project-change-hostname} script, and provide the new host name. Choose one of the following methods:

    • If your {ProjectServer} is installed with the default self-signed SSL certificates, enter the following command:

      # {project-change-hostname} new-{project-context} \
--username admin \
--password password

    • If your {ProjectServer} is installed with custom SSL certificates:

      # {project-change-hostname} new-{project-context} \
--username admin \
--password password \
--custom-cert "/root/ownca/test.com/test.com.crt" \
--custom-key "/root/ownca/test.com/test.com.key"

  2. If you have created a custom SSL certificate for the new {ProjectServer} host name, run the {Project} installation script to install the certificate. For more information about installing a custom SSL certificate, see {InstallingServerDocURL}Deploying_a_Custom_SSL_Certificate_to_Server_{project-context}[Deploying a Custom SSL Certificate to {ProjectServer}] in {InstallingServerDocTitle}.

  3. Reregister all {Project} hosts. For more information, see {ManagingHostsDocURL}Registering_Hosts_managing-hosts[Registering Hosts] in {ManagingHostsDocTitle}.

  4. On all {SmartProxyServers}, run the {Project} installation script to update references to the new host name:

    # {foreman-installer} \
--foreman-proxy-foreman-base-url https://new-{foreman-example-com} \
--foreman-proxy-trusted-hosts new-{foreman-example-com}

  5. On {ProjectServer}, list all {SmartProxyServers}:

    # {hammer-smart-proxy} list

  6. On {ProjectServer}, synchronize content for each {SmartProxyServer}:

    # {hammer-smart-proxy} content synchronize \
--id My{smart-proxy-context}_ID_

  7. If you use the virt-who agent, update the virt-who configuration files with the new host name.

  8. If you use external authentication, reconfigure {ProjectServer} for external authentication after you run the {project-change-hostname} script. For more information, see {InstallingServerDocURL}Configuring_External_Authentication_{project-context}[Configuring External Authentication] in {InstallingServerDocTitle}.