Centos7 to almalinux 8 upgrade failure

Hi Team,

We have been upgrading Centos to Almalinux8 since months now and successfully completed many server but today we have got this below errors. Kindly help with the solution if anyone has encountered it.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2024.11.21 07:38:50 =~=~=~=~=~=~=~=~=~=~=~=
sudo cat /var/log/leapp/leapp-report.txt
Risk Factor: high (error)
Title: Unable to install RHEL 8 userspace packages.
Summary: {“details”: “Command [‘systemd-nspawn’, ‘–register=no’, ‘–quiet’, ‘-D’, ‘/var/lib/leapp/scratch/mounts/root_/system_overlay’, ‘–setenv=LEAPP_UPGRADE_PATH_TARGET_RELEASE=8.10’, ‘–setenv=LEAPP_NO_RHSM=1’, ‘–setenv=LEAPP_EXPERIMENTAL=0’, ‘–setenv=LEAPP_TARGET_PRODUCT_CHANNEL=ga’, ‘–setenv=LEAPP_UPGRADE_PATH_FLAVOUR=default’, ‘–setenv=LEAPP_COMMON_TOOLS=:/etc/leapp/repos.d/system_upgrade/common/tools:/etc/leapp/repos.d/system_upgrade/el7toel8/tools’, ‘–setenv=LEAPP_NO_RHSM_FACTS=1’, ‘–setenv=LEAPP_COMMON_FILES=:/etc/leapp/repos.d/system_upgrade/common/files:/etc/leapp/repos.d/system_upgrade/el7toel8/files’, ‘–setenv=LEAPP_IPU_IN_PROGRESS=7to8’, ‘–setenv=LEAPP_UNSUPPORTED=0’, ‘–setenv=LEAPP_EXECUTION_ID=4e36bbc5-00f7-4e55-bcca-a177fabdb165’, ‘–setenv=LEAPP_HOSTNAME=inet-pubdns-sjc-dns01’, ‘dnf’, ‘install’, ‘-y’, ‘–setopt=module_platform_id=platform:el8’, ‘–setopt=keepcache=1’, ‘–releasever’, u’8.10’, ‘–installroot’, ‘/el8target’, ‘–disablerepo’, ‘*’, ‘–enablerepo’, u’almalinux8-baseos’, ‘–enablerepo’, u’almalinux8-powertools’, ‘–enablerepo’, u’almalinux8-resilientstorage’, ‘–enablerepo’, u’almalinux8-extras’, ‘–enablerepo’, u’almalinux8-ha’, ‘–enablerepo’, u’almalinux8-appstream’, ‘dnf’, ‘util-linux’, ‘dnf-command(config-manager)’, ‘–disableplugin’, ‘subscription-manager’] failed with exit code 1.”, “stderr”: “Host and machine ids are equal (d883884c744b419b95c30e835391d7bd): refusing to link journals\n/usr/lib/python2.7/site-packages/dnf/conf/config.py:250: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal\n if not value or value == ‘None’:\n\nFailed to synchronize cache for repo ‘almalinux8-baseos’, ignoring this repo.\nFailed to synchronize cache for repo ‘almalinux8-powertools’, ignoring this repo.\nFailed to synchronize cache for repo ‘almalinux8-resilientstorage’, ignoring this repo.\nFailed to synchronize cache for repo ‘almalinux8-extras’, ignoring this repo.\nFailed to synchronize cache for repo ‘almalinux8-ha’, ignoring this repo.\nSWIG director method error. Error detected when calling ‘RepoCB.end’, ignoring this repo.\nError: Unable to find a match: dnf util-linux dnf-command(config-manager)\n”}
Key: 5028175de6dcfea0cf809ced42f6e560139a5e8d

Risk Factor: high
Title: Detected custom leapp actors or files.
Summary: We have detected installed custom actors or files on the system. These can be provided e.g. by third party vendors, Red Hat consultants, or can be created by users to customize the upgrade (e.g. to migrate custom applications). This is allowed and appreciated. However Red Hat is not responsible for any issues caused by these custom leapp actors. Note that upgrade tooling is under agile development which could require more frequent update of custom actors.
The list of custom leapp actors and files:
- /usr/share/leapp-repository/repositories/system_upgrade/common/files/rpm-gpg/8/RPM-GPG-KEY-AlmaLinux-8

Remediation: [hint] In case of any issues connected to custom or third party actors, contact vendor of such actors. Also we suggest to ensure the installed custom leapp actors are up to date, compatible with the installed packages.
Key: 2064870018370ce2bde3f977cf753ed8c59848d0

Risk Factor: high
Title: Detected customized configuration for dynamic linker.
Summary: Custom configurations to the dynamic linker could potentially impact the upgrade in a negative way. The custom configuration includes modifications to /etc/ld.so.conf, custom or modified drop in config files in the /etc/ld.so.conf.d directory and additional entries in the LD_LIBRARY_PATH or LD_PRELOAD variables. These modifications configure the dynamic linker to use different libraries that might not be provided by Red Hat products or might not be present during the whole upgrade process. The following custom configurations were detected by leapp:

  • The following drop in config files were marked as custom:
    • /etc/ld.so.conf.d/vmware-tools-libraries.conf
      Remediation: [hint] Remove or revert the custom dynamic linker configurations and apply the changes using the ldconfig command. In case of possible active software collections we suggest disabling them persistently.
      Key: cc9bd972af70b7a27f66a37b11a00dcfcb73b1bc

Risk Factor: high
Title: GRUB2 core will be automatically updated during the upgrade
Summary: On legacy (BIOS) systems, GRUB2 core (located in the gap between the MBR and the first partition) cannot be updated during the rpm transaction and Leapp has to initiate the update running “grub2-install” after the transaction. No action is needed before the upgrade. After the upgrade, it is recommended to check the GRUB configuration.
Key: ac7030e05d2ee248d34f08a9fa040b352bc410a3

Risk Factor: high
Title: BIND configuration issues found
Summary: Default value of listen-on-v6 have changed, but it is not present in configuration. named service will now listen on INET6 sockets also.
Key: 45608d77dbf0f5b3c0903831a3130c641eb60889

Risk Factor: high
Title: Difference in Python versions and support in RHEL 8
Summary: In RHEL 8, there is no ‘python’ command. Python 3 (backward incompatible) is the primary Python version and Python 2 is available with limited support and limited set of packages. If you no longer require Python 2 packages following the upgrade, please remove them.
- Difference in Python versions and support in RHEL 8: Configuring basic system settings | Red Hat Product Documentation
Remediation: [hint] Please run “alternatives --set python /usr/bin/python3” after upgrade
Key: 0c98585b1d8d252eb540bf61560094f3495351f5

Risk Factor: high
Title: Packages not signed by Red Hat found on the system
Summary: The following packages have not been signed by Red Hat and may be removed during the upgrade process in case Red Hat-signed packages to be removed during the upgrade depend on them:

  • containerd.io
  • docker-ce
  • docker-ce-cli
  • docker-ce-rootless-extras
  • docker-scan-plugin
  • epel-release
  • git222
  • git222-core
  • git222-core-doc
  • git222-perl-Git
  • ius-release
    Key: 13f0791ae5f19f50e7d0d606fb6501f91b1efb2c