Troubleshooting Renaming Uyuni Server
If you change the hostname of the Uyuni Server locally, your Uyuni installation ceases to work properly. This is because the changes have not been made in the database, which prevents the changes from propagating out your clients and any proxies.
If you need to change the hostname of the Uyuni Server, you can do so using the
This script updates the settings in the PostgreSQL database and the internal structures of Uyuni.
spacewalk-hostname-rename script is part of the
The only mandatory parameter for the script is the newly configured IP address of the Uyuni Server.
Change the network settings of the server on the system level locally and remotely at the DNS server. You also need to provide configuration settings for reverse name resolution. Changing network settings is done in the same way as with renaming any other system.
Reboot the Uyuni Server to use the new network configuration and to ensure the hostname has changed.
Run the script
spacewalk-hostname-renamescript with the public IP address of the server. If the server is not using the new hostname, the script fails. Be aware that this script refreshes the pillar data for all Salt clients: the time it takes to run depends on the number of registered clients.
Skip this step if the clients are managed via a Uyuni proxy. Re-configure the clients directly managed to make them aware of the new hostname and IP address. In the Salt client configuration file, you must specify the name of the new Salt master (Uyuni Server) (the filename is
/etc/venv-salt-bundle/minionor, if you do not use the Salt bundle,
venv-salt-minionservice (if using the Salt bundle):
systemctl restart venv-salt-minion
salt-minionservice (if not using the Salt bundle):
systemctl restart salt-minion
To fully propagate the hostname to the Salt client configuration apply the high state. Applying the high state will update the hostname in the repository URLs.
Any proxy must be reconfigured.
The new server certificate and key must be copied to the proxy and the
If you use PXE boot through a proxy, you must check the configuration settings of the proxy.
On the proxy, run the