# Centos 7 to rocky8 migration fail

**URL:** <https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682>\
**Category:** Rocky Linux Help & Support\
**Tags:** unsupported, rocky-linux-8\
**Created:** [April 21, 2024, 2:15pm UTC](https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682 "2024-04-21T14:15:53Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![leeminbeom](https://avatars.discourse-cdn.com/v4/letter/l/96bed5/32.png) [@leeminbeom](https://forums.rockylinux.org/u/leeminbeom)\
**Post date:** [April 21, 2024, 2:15pm UTC](https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682/1 "2024-04-21T14:15:53Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [April 21, 2024, 3:13pm UTC](https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682/2 "2024-04-21T15:13:08Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![leeminbeom](https://avatars.discourse-cdn.com/v4/letter/l/96bed5/32.png) [@leeminbeom](https://forums.rockylinux.org/u/leeminbeom)\
**Post date:** [April 22, 2024, 2:26am UTC](https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682/3 "2024-04-22T02:26:38Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [April 22, 2024, 3:00am UTC](https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682/4 "2024-04-22T03:00:18Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [April 22, 2024, 6:36am UTC](https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682/5 "2024-04-22T06:36:54Z")

</div>

> [@leeminbeom](#):
>
> After upgrading from centos 7 to centos 8,  
> Should I upgrade to rocky8?

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.

---

<div class="post-metadata">

**Author:** ![mercury46](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/mercury46/32/849_2.png) [@mercury46](https://forums.rockylinux.org/u/mercury46)\
**Post date:** [June 13, 2024, 10:05am UTC](https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682/6 "2024-06-13T10:05:19Z")

</div>

Hi there,

I had the same problem as described. My solution is as following:

1.) Deinstall the following components  
yum erase -y _java_  
yum erase -y _brotli_  
yum erase -y openssl11-libs

2.) Do an Elevate-Upgrade to migrate directly from CentOS 7 to Rocky 8. It is mostly those commands:  
yum clean all  
yum makecache fast  
yum update -y  
yum install -y [http://repo.almalinux.org/elevate/elevate-release-latest-el$](http://repo.almalinux.org/elevate/elevate-release-latest-el$)(rpm --eval %rhel).noarch.rpm  
yum install -y leapp-upgrade leapp-data-rocky  
leapp preupgrade  
leapp answer --section remove\_pam\_pkcs11\_module\_check.confirm=True  
export LEAPP\_OVL\_SIZE=3584  
leapp upgrade

3.) Postmigrationtasks are documented here

> **[Chapter 8. Performing post-upgrade tasks Red Hat Enterprise Linux 8...](https://access.redhat.com/documentation/de-de/red_hat_enterprise_linux/8/html/upgrading_from_rhel_7_to_rhel_8/performing-post-upgrade-tasks-rhel-7-to-rhel-8_upgrading-from-rhel-7-to-rhel-8)**
>
> Access Red Hat’s knowledge, guidance, and support through your subscription.

You might need to reconfigure your firewall and reactivate SELinux.

4.) Reinstall your Java (choose correct package) and Brotli  
dnf install -y java-11-openjdk-headless brotli

5.) You need to reinstall all programs that are not part of the base and epel repos!!! But fortunately the config is still there.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [August 12, 2024, 10:05am UTC](https://forums.rockylinux.org/t/centos-7-to-rocky8-migration-fail/13682/7 "2024-08-12T10:05:20Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
