Short tip: Migration to SUSE Multi-Linux Manager 5.1.3 fails
During a recent migration from SUSE Manager 4.3.16 to SUSE Multi-Linux Manager 5.1.3, I encountered the following error:
1# mgradm podman migrate oldserver.corp.lan
2...
313:37AM INF Run podman volume rm etc-tls
413:37AM ??? Reindexing database. This may take a while, please do not cancel it!
513:37AM ??? psql: error:
613:37AM ??? connection to server at "db" (dec2:1e47:14a7:8163::10), port 5432 failed: FATAL: no pg_hba.conf entry for host "dec2:1e47:14a7:8163::11", user "susemanager", database "susemanager", SSL encryption
7connection to server at "db" (dec2:1e47:14a7:8163::10), port 5432 failed: FATAL: no pg_hba.conf entry for host "dec2:1e47:14a7:8163::11", user "susemanager", database "susemanager", no encryption
813:37AM ERR error="cannot run PostgreSQL finalize script: failed to run uyuni-finalize-pgsql container: exit status 2"
9Error: cannot run PostgreSQL finalize script: failed to run uyuni-finalize-pgsql container: exit status 2
The usual source of the error - an incorrect PostgreSQL configuration - has been ruled out. With the release of Uyuni 2026.04, a set of symptoms which pointed in a similar direction was discussed on the mailing list. It appears that the database container's upgrade mechanism failed to reload the database configuration after changes were made. The affected version of mgradm is 5.1.26:
1# rpm -qi mgradm
2Name : mgradm
3Version : 5.1.26
4Release : slfo.1.1.1
5Architecture: x86_64
6Install Date: Wed 06 May 2026 13:37:42 AM CEST
7Group : System/Management
8Size : 18532436
9License : Apache-2.0
10Signature : RSA/SHA512, Fri 27 Mar 2026 10:17:37 AM CET, Key ID fec28eaf09d9ea69
11Source RPM : uyuni-tools-5.1.26-slfo.1.1.1.src.rpm
12Build Date : Mon 23 Mar 2026 08:04:55 AM CET
13Build Host : reproducible
14Packager : https://www.suse.com/
15Vendor : SUSE LLC <https://www.suse.com/>
16URL : https://github.com/uyuni-project/uyuni-tools
17Summary : Command line tool to install and update SUSE Multi-Linux Manager
18Description :
19mgradm is a convenient tool to install and update SUSE Multi-Linux Manager components as containers running
20either on Podman or a Kubernetes cluster.
21Distribution: SUSE Linux 16
As I didn’t have the MLM 5.1 source code available, but a recent migration had gone smoothly, I decided on the spot to downgrade to the previous version of the mgradm tool:
1# zypper install --oldpackage mgradm-5.1.24 mgradm-bash-completion-5.1.24
The latest versions of the tool:
| Version | Date | MLM version |
|---|---|---|
| 5.1.26 | 23.03.2026 | 5.1.3 |
| 5.1.24 | 16.01.2026 | 5.1.2 |
| 5.1.23 | 21.11.2025 | 5.1.1 |
| 5.1.22 | 14.10.2025 | 5.1.1 |
| 5.1.18 | 24.07.2025 | 5.1 |
As a result, version 5.1.2 was installed during the migration rather than MLM 5.1.3. However, a subsequent upgrade was carried out without any problems:
1# mgradm podman upgrade