dnf_transaction_check: Cannot calculate, check, test, or perform the upgrade transaction.

[brownsugar]

Describe the bug
Error during TargetTransactionCheck process, didn't find a proper way to fix it.

INFO - stdout: ==> Processing phase `TargetTransactionCheck`
INFO - stdout: ====> * report_set_target_release
INFO - stdout:         Reports information related to the release set in the subscription-manager after the upgrade.
INFO - stdout: ====> * missing_gpg_keys_inhibitor
INFO - stdout:         Check if all used target repositories have signing gpg keys
INFO - stdout: ====> * adjust_local_repos
INFO - stdout:         Adjust local repositories to the target user-space container.
INFO - stdout: ====> * dnf_transaction_check
INFO - stderr: 2025-02-12 02:14:50.279 ERROR    PID: 32430 leapp.workflow.TargetTransactionCheck.dnf_transaction_check: Cannot calculate, check, test, or perform the upgrade transaction.
INFO - stdout:         This actor tries to solve the RPM transaction to verify the all package dependencies can be successfully resolved.
...
ERROR - Command ['/usr/bin/leapp', 'preupgrade'] failed with return code 1
ERROR - Failed: doing the conversion. The reason: Command '['/usr/bin/leapp', 'preupgrade']' returned non-zero exit status 1.

I got the following error at first, then I edited /etc/yum.repos.d/pgdg-redhat-all.repo to comment out the corresponding config and it worked, then encountered the error above.

INFO - stdout:     Stdout: Extra Packages for Enterprise Linux 8 - x86_64   13 MB/s |  14 MB     00:01
INFO - stdout:             Alma Extra Packages for Enterprise Linux 8 - x8  13 MB/s |  14 MB     00:01
INFO - stdout:             Alma Extra Packages for Enterprise Linux 8 - x8 6.6 MB/s | 5.5 MB     00:00
INFO - stdout:             Alma Extra Packages for Enterprise Linux 8 - x8 3.2 MB/s | 2.6 MB     00:00
INFO - stdout:             Alma PostgreSQL 10 for RHEL/CentOS 8 - x86_64 -  89  B/s | 146  B     00:01
INFO - stdout:     Stderr: No matches found for the following disable plugin patterns: subscription-manager
INFO - stdout:             Repository extras is listed more than once in the configuration
INFO - stdout:             Repository extras-source is listed more than once in the configuration
INFO - stdout:             Errors during downloading metadata for repository 'alma-pgdg10-source':
INFO - stdout:               - Status code: 404 for https://download.postgresql.org/pub/repos/yum/srpms/10/redhat/rhel-8-x86_64/repodata/repomd.xml (IP: 87.238.57.227)
INFO - stdout:             Error: Failed to download metadata for repo 'alma-pgdg10-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

System info:

Product version: Plesk Obsidian 18.0.67.2
     OS version: CentOS 7.9.2009 x86_64
     Build date: 2025/02/05 19:00
       Revision: f88f36449702f778b1cf43d8886ff00b56f2a1e5

All error logs are attached in the archive below.

Feedback archive
Please attach a feedback archive to the bug report.
centos2alma_feedback.zip

[SandakovMM]

The repository for PostgreSQL 10 (https://download.postgresql.org/pub/repos/yum/srpms/10) is no longer available, preventing the upgrade of this installation. Here are two options to continue with the conversion:

• Reinstall the PostgreSQL database using the Plesk installer.
• Upgrade PostgreSQL to the latest available version, 12, from download.postgresql.org.

[brownsugar]

Hi @SandakovMM thanks for replying.

I was using PostgreSQL 9.6 and already upgraded to 15 before doing the conversion.
I also had the pgdg-redhat-all.repo configured to use the archive endpoint for the deprecated version and the alma-pgdg10-source error was solved.

Is this error (the TargetTransactionCheck error) still related to pgdg10? (postgresql10 was removed as well)
I tried another shot but comes with the same error:

Here's my package list:

# yum list | grep postgresql1
postgresql15.x86_64                     15.11-1PGDG.rhel7            @pgdg15
postgresql15-contrib.x86_64             15.11-1PGDG.rhel7            @pgdg15
postgresql15-libs.x86_64                15.11-1PGDG.rhel7            @pgdg15
postgresql15-server.x86_64              15.11-1PGDG.rhel7            @pgdg15
postgresql12.x86_64                     12.22-1PGDG.rhel7            pgdg12
postgresql12-contrib.x86_64             12.22-1PGDG.rhel7            pgdg12
postgresql12-devel.x86_64               12.22-1PGDG.rhel7            pgdg12
postgresql12-docs.x86_64                12.22-1PGDG.rhel7            pgdg12
postgresql12-libs.x86_64                12.22-1PGDG.rhel7            pgdg12
postgresql12-llvmjit.x86_64             12.22-1PGDG.rhel7            pgdg12
postgresql12-odbc.x86_64                16.00.0000-1PGDG.rhel7       pgdg12
postgresql12-odbc-debuginfo.x86_64      12.02.0000-1PGDG.rhel7       pgdg-common
postgresql12-plperl.x86_64              12.22-1PGDG.rhel7            pgdg12
postgresql12-plpython.x86_64            12.22-1PGDG.rhel7            pgdg12
postgresql12-plpython3.x86_64           12.22-1PGDG.rhel7            pgdg12
postgresql12-pltcl.x86_64               12.22-1PGDG.rhel7            pgdg12
postgresql12-server.x86_64              12.22-1PGDG.rhel7            pgdg12
postgresql12-tcl.x86_64                 3.1.0-1PGDG.rhel7            pgdg12
postgresql12-test.x86_64                12.22-1PGDG.rhel7            pgdg12
postgresql13.x86_64                     13.19-1PGDG.rhel7            pgdg13
postgresql13-contrib.x86_64             13.19-1PGDG.rhel7            pgdg13
postgresql13-devel.x86_64               13.19-1PGDG.rhel7            pgdg13
postgresql13-docs.x86_64                13.19-1PGDG.rhel7            pgdg13
postgresql13-libs.x86_64                13.19-1PGDG.rhel7            pgdg13
postgresql13-llvmjit.x86_64             13.19-1PGDG.rhel7            pgdg13
postgresql13-odbc.x86_64                16.00.0000-1PGDG.rhel7       pgdg13
postgresql13-plperl.x86_64              13.19-1PGDG.rhel7            pgdg13
postgresql13-plpython3.x86_64           13.19-1PGDG.rhel7            pgdg13
postgresql13-pltcl.x86_64               13.19-1PGDG.rhel7            pgdg13
postgresql13-server.x86_64              13.19-1PGDG.rhel7            pgdg13
postgresql13-test.x86_64                13.19-1PGDG.rhel7            pgdg13
postgresql15-devel.x86_64               15.11-1PGDG.rhel7            pgdg15
postgresql15-docs.x86_64                15.11-1PGDG.rhel7            pgdg15
postgresql15-llvmjit.x86_64             15.11-1PGDG.rhel7            pgdg15
postgresql15-odbc.x86_64                16.00.0000-1PGDG.rhel7       pgdg15
postgresql15-plperl.x86_64              15.11-1PGDG.rhel7            pgdg15
postgresql15-plpython3.x86_64           15.11-1PGDG.rhel7            pgdg15
postgresql15-pltcl.x86_64               15.11-1PGDG.rhel7            pgdg15
postgresql15-tcl.x86_64                 3.1.0-1PGDG.rhel7            pgdg15
postgresql15-test.x86_64                15.11-1PGDG.rhel7            pgdg15

And the latest feedback:
centos2alma_feedback.zip

[SandakovMM]

Hi @brownsugar,
I have identified the issue detailed in /var/log/leapp/leapp-report.txt (the first instance marked as error):

Risk Factor: high (error)
Title: DNF execution failed with non zero exit code.
Summary: {"hint": "If there was a problem reaching remote content (see stderr output) and proxy is configured in the YUM/DNF configuration file, the proxy configuration is likely causing this error. 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, it will be used during some parts of the upgrade instead of original /etc/dnf/dnf.conf. In such case the configuration will also be applied to the target system. Note that /etc/dnf/dnf.conf needs to be still configured correctly for your current system to pass the early phases of the upgrade process.", "STDERR": "No matches found for the following disable plugin patterns: subscription-manager\nRepository extras is listed more than once in the configuration\nRepository extras-source is listed more than once in the configuration\nErrors during downloading metadata for repository 'alma-pgdg13-updates-debuginfo':\n  - Status code: 404 for https://download.postgresql.org/pub/repos/yum/debug/13/redhat/rhel-8-x86_64/repodata/repomd.xml (IP: 147.75.85.69)\nError: Failed to download metadata for repo 'alma-pgdg13-updates-debuginfo': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried\n", "STDOUT": "Extra Packages for Enterprise Linux 8 - x86_64   12 MB/s |  14 MB     00:01    \nAlma Extra Packages for Enterprise Linux 8 - x8  13 MB/s |  14 MB     00:01    \nAlma Extra Packages for Enterprise Linux 8 - x8 6.3 MB/s | 5.5 MB     00:00    \nAlma Extra Packages for Enterprise Linux 8 - x8 3.6 MB/s | 2.6 MB     00:00    \nAlma PostgreSQL 13 for RHEL/CentOS 8 - x86_64 - 101  B/s | 146  B     00:01    \n"}
Key: 1e26c8b86cec72c25c04ca045d2b0ed3e8ca2df5
----------------------------------------

Essentially, it indicates that the repository https://download.postgresql.org/pub/repos/yum/debug/13/redhat/rhel-8-x86_64/repodata/repomd.xml does not exist. It appears that PostgreSQL debug information is not available for RHEL 8 systems. So to proceed with the conversion, you should comment out pgdg13-updates-debuginfo and pgdg12-updates-debuginfo in your /etc/yum.repos.d/pgdg-redhat-all.repo file.

[brownsugar]

Thank you @SandakovMM, that helps!
I've successfully passed the conversion process and did a reboot, but then I bumped into the same issue as this one: #313

2025-02-15 02:14:32,002 - INFO - Command ['/usr/bin/rpm', '-e', '--nodeps', 'MariaDB-client', 'MariaDB-compat', 'MariaDB-common', 'MariaDB-server', 'MariaDB-shared'] finished successfully
2025-02-15 02:14:32,002 - INFO - Running: ['/usr/bin/yum', 'install', '--repo', 'alma-mariadb', '-y', 'MariaDB-client', 'MariaDB-server']. Output:
2025-02-15 02:14:32,156 - INFO - stdout: Loaded plugins: fastestmirror, product-id, rhsm-auto-add-pools, search-disabled-
2025-02-15 02:14:32,158 - INFO - stderr: Command line error: no such option: --repo
2025-02-15 02:14:32,158 - INFO - stdout:               : repos
2025-02-15 02:14:32,158 - INFO - stdout: Usage: yum [options] COMMAND
2025-02-15 02:14:32,171 - INFO - stdout:
2025-02-15 02:14:32,171 - ERROR - Command ['/usr/bin/yum', 'install', '--repo', 'alma-mariadb', '-y', 'MariaDB-client', 'MariaDB-server'] failed with return code 1
2025-02-15 02:14:32,171 - ERROR - Failed: update modern mariadb. The reason: Command '['/usr/bin/yum', 'install', '--repo', 'alma-mariadb', '-y', 'MariaDB-client', 'MariaDB-server']' returned non-zero exit status 1.

2025-02-15 02:14:32,910 - DEBUG - Sent error report
2025-02-15 02:14:32,921 - DEBUG - Trying to send status of conversion by report-update utility '/root/parallels/report-update'
2025-02-15 02:14:34,452 - ERROR - centos2alma process has failed. Error: Failed: update modern mariadb. The reason: Command '['/usr/bin/yum', 'install', '--repo', 'alma-mariadb', '-y', 'MariaDB-client', 'MariaDB-server']' returned non-zero exit status 1.

And...it's not revertable:

2025-02-15 02:24:24,771 - INFO - stderr: Exception: Failed to solve dependencies:
2025-02-15 02:24:24,843 - INFO - stdout:
2025-02-15 02:24:24,851 - INFO - stderr: MariaDB-client-10.5.28-1.el8.x86_64 requires libtinfo.so.6()(64bit)
2025-02-15 02:24:24,851 - INFO - stderr: MariaDB-client-10.5.28-1.el8.x86_64 requires libc.so.6(GLIBC_2.28)(64bit)
2025-02-15 02:24:24,851 - INFO - stderr: MariaDB-client-10.5.28-1.el8.x86_64 requires libcrypt.so.1(XCRYPT_2.0)(64bit)
2025-02-15 02:24:24,851 - INFO - stderr: MariaDB-client-10.5.28-1.el8.x86_64 requires libncurses.so.6()(64bit)
2025-02-15 02:24:24,851 - INFO - stderr: exit status 1
2025-02-15 02:24:24,851 - ERROR - Command ['/usr/sbin/plesk', 'installer', 'update'] failed with return code 1
2025-02-15 02:24:24,851 - ERROR - Failed: re-installing plesk components. The reason: Command '['/usr/sbin/plesk', 'installer', 'update']' returned non-zero exit status 1.

but that's fine I've already created a server snapshot.
I didn't notice the command cat /boot/grub2/grub.cfg to execute before I restored the snapshot...I'll check it using a cloned instance later in my morning.

The archive: centos2alma_feedback.zip