Skip to content

Commit 198777d

Browse files
committed
Fix the documentation on how to rename the server (bsc#1229825)
1 parent 964cc72 commit 198777d

File tree

2 files changed

+26
-8
lines changed

2 files changed

+26
-8
lines changed

CHANGELOG.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
- Fix the hostname rename page for containers (bsc#1229825)
12
- Documented TFTP file synchronization after migrating a 4.3 proxy in
23
Installation and Upgrade Guide (bsc#1244427)
34
- Added Role-Based Access Control (RBAC) chapter to Administration Guide

modules/administration/pages/troubleshooting/tshoot-hostname-rename.adoc

Lines changed: 25 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -35,38 +35,55 @@ This is because the changes have not been made in the database, which prevents t
3535

3636
== Rename Server
3737

38-
If you need to change the hostname of the {productname} Server, you can do so using the [command]``spacewalk-hostname-rename`` script.
39-
This script updates the settings in the {postgresql} database and the internal structures of {productname}.
38+
If you need to change the hostname of the {productname} Server, you can do so using the [command]``mgradm server rename`` command.
39+
This command updates the settings in the {postgresql} database and the internal structures of {productname}.
4040

4141

4242

4343
=== Server Configuration
4444

45-
The [command]``spacewalk-hostname-rename`` script is part of the [package]``spacewalk-utils`` package.
45+
The command takes no mandatory parameter, but can take the new hostname if it is not the one from the container host.
4646

47-
The only mandatory parameter for the script is the newly configured IP address of the {productname} Server.
4847

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

51+
.Procedure: Prepare the configuration file for the SSL CA password
52+
. Write a [path]``config.yaml`` file with content like the following:
53+
+
54+
[source,shell]
55+
----
56+
ssl:
57+
password: "<THE CA PASSWORD>"
58+
----
5059

5160
.Procedure: Renaming {productname} Server
5261
. Change the network settings of the server on the system level locally and remotely at the DNS server.
5362
You also need to provide configuration settings for reverse name resolution.
5463
Changing network settings is done in the same way as with renaming any other system.
5564
. Reboot the {productname} Server to use the new network configuration and to ensure the hostname has changed.
56-
. On the container host, from the command line, execute the following command to configure the public IP address of the server:
65+
. On the container host, from the command line, execute the following command. Add [command]``-c config.yaml`` if you created the file to store the SSL CA password:
5766

5867
+
5968

6069
[source,shell]
6170
----
62-
mgrctl exec -ti -- spacewalk-hostname-rename <PUBLIC_IP_ADDRESS>
71+
mgradm server rename
6372
----
6473

6574
+
6675

67-
If the server is not using the new hostname, the script fails.
68-
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.
76+
If the new hostname is not resolvable, the command fails.
77+
78+
The renaming procedure also takes place during the restart of the server container.
79+
The logs can be found by running this command:
80+
81+
[source,shell]
82+
----
83+
mgrctl exec -ti -- journalctl -u uyuni-update-config
84+
----
6985

86+
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.
7087

7188

7289
=== Directly Managed Clients Reconfiguration

0 commit comments

Comments
 (0)