This section contains some common problems you might encounter with Uyuni upgrades, and solutions to resolving them.
To get more information about an upgrade problem, check the migration log file.
The log file is located at
/var/log/rhn/migration.log on the system you are upgrading.
Check the available disk space before you begin migration.
We recommend locating
/var/lib/pgsql on separate XFS file systems.
When you are setting up a separate file system, edit
/etc/fstab and remove the
Reboot the server to pick up the changes.
If you need to retry setting up the target system, follow these steps:
Stop PostgreSQL and remove
Set the target system hostname to match the source system hostname.
/etc/hostsfile, and correct it if necessary.
/etc/setup_env.shon the target system, and ensure the database name is set:
Reboot the target system.
If the schema upgrade fails, the database version check and all the other spacewalk services do not start.
spacewalk-service start for more information and hints how to proceed.
You can also run the version check directly:
systemctl status uyuni-check-database.service
journalctl -u uyuni-check-database.service
These commands print debug information if you do not want to run the more general
Sometimes, the Web UI will not load after migration. This is usually caused by browser caching, if the new system has the same hostname and IP address as the old system. This duplication can confuse some browsers.
This issue is resolved by clearing the cache and reloading the page. In most browsers, you can do this quickly by pressing Ctrl+F5.
This is not a valid scenario. Normally you migrate a traditional client to a Salt minion without deleting the client. Salt automatically detects that you have a traditional client and does the necessary changes itself. But if you somehow deleted the traditional client and want to register it as a Salt minion again, you have to do the following steps on the client before registering it as Salt minion:
Remove the following file:
Remove the following package: