Suse-Multi-Linux-Manager on cstan.io

Short tip: Migration to SUSE Multi-Linux Manager 5.1.3 fails

Thu, 07 May 2026 00:00:00 +0000

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:

Short tip: transactional-update and breaking post-scripts

Tue, 12 Aug 2025 00:00:00 +0000

I recently updated an openSUSE Leap Micro 6.1 machine running Uyuni 2025.05 before upgrading to Uyuni 2025.07:

1# transactional-update
2# reboot

After running transactional-update (as suggested by the Uyuni documentation) and rebooting the system, Uyuni couldn't be started anymore:

1# mgradm start
24:36PM INF Welcome to mgradm
34:36PM INF Executing command: start
4Error: failed to start systemd uyuni-db.service: exit status 1; failed to start systemd uyuni-server.service: exit status 1
5
6# podman ps
7CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES

I found out that Podman isn't able to start the containers anymore:

SUSECON 2025

Mon, 07 Apr 2025 00:00:00 +0000

From 10.03 to 14.03.2025 the SUSECON took place in Orlando. Compared to the previous iteration of the conference, the 13th event of its kind lasted almost 2 days longer. The first day consisted of an exclusive event for partners, the last day ended for most participants at noon after some final presentations. The motto was once again "Choice happens".

Note 🎙️

On the occasion of SUSECON 2025, a special was published in the FOCUS ON: Linux-Podcast. In addition to a Recap, there is also an Interview with parts of the SUSE Multi-Linux Manager team.