Troubleshooting Renaming SUSE Manager Server
If you change the hostname of the SUSE Manager Server locally, your SUSE Manager 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 SUSE Manager Server, you can do so using the
This script updates the settings in the PostgreSQL database and the internal structures of SUSE Manager.
spacewalk-hostname-rename script is part of the
The only mandatory parameter for the script is the newly configured IP address of the SUSE Manager 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 SUSE Manager 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 minion: the time it takes to run depends on the number of registered Salt systems.
Re-configure your clients to make your environment aware of the new hostname and IP address. In the Salt minion configuration file
/etc/salt/minion, you must specify the name of the new Salt master (SUSE Manager Server):
Once this is changed, restart the
systemctl restart salt-minion
To fully propagate the hostname to the minion configuration apply the high state. Applying the high state will update the hostname in the repository URLs.
Traditional clients have the
/etc/sysconfig/rhn/up2date configuration file that must be changed.
With a re-activation key you can re-register traditional clients (if there are any).
For more information, see Register on the Command Line (Salt).
If you use PXE boot through a proxy, you must check the configuration settings of the proxy.
On the proxy, run the