Troubleshooting Renaming SUSE Multi-Linux Manager Server

If you change the hostname of the SUSE Multi-Linux Manager Server locally, your SUSE Multi-Linux 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.

1. Rename Server

If you need to change the hostname of the SUSE Multi-Linux Manager Server, you can do so using the mgradm server rename command. This command updates the settings in the PostgreSQL database and the internal structures of SUSE Multi-Linux Manager.

1.1. Server Configuration

The command takes no mandatory parameter, but can take the new hostname if it is not the one from the container host.

In case any SSL certificate needs to be generated to match the new hostname, the SSL CA password needs to be provided. This is safely achieved using a configuration file

Procedure: Prepare the configuration file for the SSL CA password

Write a config.yaml file with content like the following:
```
ssl:
  password: "<THE CA PASSWORD>"
```

Procedure: Renaming SUSE Multi-Linux 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 Multi-Linux Manager Server to use the new network configuration and to ensure the hostname has changed.
On the container host, from the command line, execute the following command. Add -c config.yaml if you created the file to store the SSL CA password:
```
mgradm server rename
```
If the new hostname is not resolvable, the command fails.

The renaming procedure also takes place during the restart of the server container. The logs can be found by running this command:

mgrctl exec -ti -- journalctl -u uyuni-update-config

Be aware that this command triggers a refresh of the pillar data for all Salt clients when restarting the server container: the time it takes to run depends on the number of registered clients.

1.2. Directly Managed Clients Reconfiguration

Skip this procedure if clients are managed via a SUSE Multi-Linux Manager proxy.

With the following procedure, reconfigure directly managed clients to make them aware of the new hostname and IP address.

Procedure: Reconfiguring Directly Managed Clients

On the every client, in the Salt client configuration file, specify the name of the new Salt master (SUSE Multi-Linux Manager Server). The filename is /etc/venv-salt-minion/minion.d/susemanager.conf or, if you do not use the Salt bundle, /etc/salt-minion/minion.d/susemanager.conf:
```
master: <new_hostname>
```
On every client, restart Salt service. Either run:
```
systemctl restart venv-salt-minion
```
Or, if you do not use the Salt bundle, run:
```
systemctl restart salt-minion
```

1.3. Client Connection with Applying High State

Finally, 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.

2. Reconfigure Proxy

Every proxy must be reconfigured. The new server certificate and key must be copied to the proxy. For more information, see Install SUSE Multi-Linux Manager Proxy.

If you use PXE boot through a proxy, you must check the configuration settings of the proxy. If you use PXE boot through non-containerized SUSE Multi-Linux Manager Proxy 4.3, tftpsync needs to be reconfigured.

On the container host, execute:

mgrctl exec -ti -- configure-tftpsync.sh