This is not a direct issue with the conversion tool, but it is an issue that breaks the conversion. If the system has postgres present, installed via the official pgdg-redhat-repo-latest package from Postgres, the Leapp tool tries to build a new repo file that includes version of Postgres that do not exist for Alma 9 / EL9. It will also enable versions of Postgres that you might not have wanted, if you'd previously used dnf config-manager to disable them.
The file you end up with is /etc/leapp/files/vendors.d/postgresql.repo
It will include references for repos from el9-pgdg13 and older, back to at least 11 perhaps even earlier. el9-pgdg14 is the oldest Postgres has published now: https://download.postgresql.org/pub/repos/yum/
It will also include newer versions through 18, and enable them, so if you'd previously disabled newer postgres repos intentionally, to version lock, you may end up with a newer version than you wanted if you don't also fix that issue.
When the alma 8 to 9 conversion tool calls 'leapp preupgrade' with version 13 and older present, it causes a failure:
2026-07-01 07:30:27.480055 [ERROR] Actor: target_userspace_creator
Message: Unable to install RHEL 9 userspace packages.
Summary:
Details: DNF failed to install userspace packages, likely due to the proxy configuration detected in the YUM/DNF configuration file. Make sure the proxy is properly configured in /etc/dnf/dnf.conf. It's also possible the proxy settings in the DNF configuration file are incompatible with the target system. A compatible configuration can be placed in /etc/leapp/files/dnf.conf which, if present, will be used during the upgrade instead of /etc/dnf/dnf.conf. In such case the configuration will also be applied to the target system.
Stderr: Host and machine ids are equal (2b5170136c1946efb61c067970814c42): refusing to link journals
No matches found for the following disable plugin patterns: subscription-manager
Importing GPG key 0x08B40D20:
Userid : "PostgreSQL RPM Repository <pgsql-pkg-yum@lists.postgresql.org>"
Fingerprint: D4BF 08AE 67A0 B4C7 A1DB CCD2 40BC A2B4 08B4 0D20
From : /etc/pki/rpm-gpg/PGDG-RPM-GPG-KEY-RHEL
Importing GPG key 0x08B40D20:
Userid : "PostgreSQL RPM Repository <pgsql-pkg-yum@lists.postgresql.org>"
Fingerprint: D4BF 08AE 67A0 B4C7 A1DB CCD2 40BC A2B4 08B4 0D20
From : /etc/pki/rpm-gpg/PGDG-RPM-GPG-KEY-RHEL
Errors during downloading metadata for repository 'el9-pgdg13':
- Status code: 410 for https://download.postgresql.org/pub/repos/yum/13/redhat/rhel-9-x86_64/repodata/repomd.xml (IP: 192.0.2.1)
Error: Failed to download metadata for repo 'el9-pgdg13': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
If you edit /etc/leapp/files/vendors.d/postgresql.repo before running the almalinux8to9 utility, you can disable or remove versions newer than you want, and versions 13 and older, then the preupgrade step won't fail.
If you've already run into this failure, and don't want to start over, just edit /etc/leapp/files/vendors.d/postgresql.repo to remove the version 13 and older targets, disable the newer ones if you dont want them, and run ./almalinux8to9 --resume
This is not a direct issue with the conversion tool, but it is an issue that breaks the conversion. If the system has postgres present, installed via the official pgdg-redhat-repo-latest package from Postgres, the Leapp tool tries to build a new repo file that includes version of Postgres that do not exist for Alma 9 / EL9. It will also enable versions of Postgres that you might not have wanted, if you'd previously used dnf config-manager to disable them.
The file you end up with is /etc/leapp/files/vendors.d/postgresql.repo
It will include references for repos from el9-pgdg13 and older, back to at least 11 perhaps even earlier. el9-pgdg14 is the oldest Postgres has published now: https://download.postgresql.org/pub/repos/yum/
It will also include newer versions through 18, and enable them, so if you'd previously disabled newer postgres repos intentionally, to version lock, you may end up with a newer version than you wanted if you don't also fix that issue.
When the alma 8 to 9 conversion tool calls 'leapp preupgrade' with version 13 and older present, it causes a failure:
If you edit /etc/leapp/files/vendors.d/postgresql.repo before running the almalinux8to9 utility, you can disable or remove versions newer than you want, and versions 13 and older, then the preupgrade step won't fail.
If you've already run into this failure, and don't want to start over, just edit /etc/leapp/files/vendors.d/postgresql.repo to remove the version 13 and older targets, disable the newer ones if you dont want them, and run ./almalinux8to9 --resume