Centos 7 to rocky8 migration fail

Rocky Linux General
,
1

Hi
A fail occurred during centos 7 to rocky8 migration.
Does anyone know what the problem is?

leapp preupgrade

2024-04-21 23:10:13.025722 [ERROR] Actor: dnf_transaction_check
Message: DNF execution failed with non zero exit code.
STDOUT:
Last metadata expiration check: 0:01:12 ago on Sun Apr 21 23:08:50 2024.

STDERR:
Failed to create directory /var/lib/leapp/el8userspace//sys/fs/selinux: Read-only file system
Failed to create directory /var/lib/leapp/el8userspace//sys/fs/selinux: Read-only file system
No matches found for the following disable plugin patterns: subscription-manager
Repository extras is listed more than once in the configuration
Warning: Package marked by Leapp to install not found in repositories metadata: python3-nss ldns-utils
Warning: Package marked by Leapp to upgrade not found in repositories metadata: gpg-pubkey
Transaction check:

Problem: package javapackages-tools-5.3.0-2.module+el8.3.0+74+855e3f5d.noarch from rocky8-powertools requires javapackages-filesystem = 5.3.0-2.module+el8.3.0+74+855e3f5d, but none of the providers can be installed

  • cannot install both javapackages-filesystem-5.3.0-2.module+el8.3.0+74+855e3f5d.noarch from rocky8-powertools and javapackages-filesystem-5.3.0-2.module+el8.3.0+125+5da1ae29.noarch from rocky8-appstream
  • package ivy-local-5.3.0-2.module+el8.3.0+74+855e3f5d.noarch from rocky8-powertools requires javapackages-tools = 5.3.0-2.module+el8.3.0+74+855e3f5d, but none of the providers can be installed
  • cannot install the best candidate for the job
  • conflicting requests
    --------------------------------------------------------------------------------------[root@sharingweb01 ~]# rpm -qi leapp
    Name : leapp
    Version : 0.14.0
    Release : 1.el7
    Architecture: noarch
1 Like
2

Rocky does not support upgrading from CentOS 7. Install a new Rocky system and migrate your data from the CentOS 7 machine to the new Rocky one.

3

After upgrading from centos 7 to centos 8,
Should I upgrade to rocky8?

4

The situation is the same and you will likely face the same exact error. It won’t be a supported system here or with the CentOS community. You are recommended to install a new system and migrate your data.

Based on the issue you have, you may want to remove javapackages-tools before performing the upgrade and install it after finishing. Other than that, if you insist on performing an upgrade (I will assume you are using ELevate), you will need to work with the maintainers of the software you’re using to work through any other issues you may face.

5

Each RHEL major version is a distinct distro. Same is true for CentOS and Rocky.
Yes, one can and often does call replacing one distro with newer major version an upgrade.
Some might call it migration.

What CentOS and Rocky do support is fresh install followed by deploying appropriate config and transfer of user data. If one has to work with only one machine and cannot retain old “data partitions”, then one has to restore user data from backups.

IMHO, what the Red Hat’s leapp (and derivatives, like ELevate) try to do is automated in-place conversion from one distro to another. Some systems tend to have configurations/customizations set “by hand” – something no automation is prepared to parse and thus will fail. One really has to talk to the maintainers of those conversion tools in order to get them handle more cases.

Personally, I rather install fresh. (I have a procedure for that, so it is “routine” by now.)

CentOS [Linux] 8 is dead. It has been dead over three years now.

When CentOS 8 was still alive, it was possible to sidegrade CentOS 8.4 → Rocky 8.4 (and later CentOS 8.5 → Rocky 8.5). These were “safe and supported conversions” because those distros were practically identical.

There exists CentOS Stream 8, but that distro differs from the EL8 distros. It will also die before CentOS 7.