Error Migrating from Centos 7

Support
1

Hi there,
the pre-upgrade goes fair and GREEN but when i run:

leapp upgrade

it downloads all the packages and run the transaction

The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
2022-02-22 12:43:06.469 ERROR    PID: 8110 leapp.workflow.Download.dnf_package_download: DNF execution failed: 

============================================================
                           ERRORS                           
============================================================

2022-02-22 12:43:06.887922 [ERROR] Actor: dnf_package_download
Message: DNF execution failed with non zero exit code.
STDOUT:
Last metadata expiration check: 0:00:53 ago on Tue Feb 22 12:41:04 2022.
...

and then

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
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/epel.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/epel.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/epel.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/epel-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/epel-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/epel-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Warning: Packages marked by Leapp for install not found in repositories metadata: ldns-utils
Warning: Packages marked by Leapp for upgrade not found in repositories metadata: gpg-pubkey
RPM: warning: Generating 6 missing index(es), please wait...
Error: Transaction test error:
  file /usr/lib64/.libcrypto.so.1.1.1k.hmac from install of openssl-libs-1:1.1.1k-5.el8_5.x86_64 conflicts with file from package openssl11-libs-1:1.1.1k-2.el7.x86_64
  file /usr/lib64/.libssl.so.1.1.1k.hmac from install of openssl-libs-1:1.1.1k-5.el8_5.x86_64 conflicts with file from package openssl11-libs-1:1.1.1k-2.el7.x86_64
  file /usr/lib64/engines-1.1/afalg.so from install of openssl-libs-1:1.1.1k-5.el8_5.x86_64 conflicts with file from package openssl11-libs-1:1.1.1k-2.el7.x86_64
  file /usr/lib64/engines-1.1/capi.so from install of openssl-libs-1:1.1.1k-5.el8_5.x86_64 conflicts with file from package openssl11-libs-1:1.1.1k-2.el7.x86_64
  file /usr/lib64/engines-1.1/padlock.so from install of openssl-libs-1:1.1.1k-5.el8_5.x86_64 conflicts with file from package openssl11-libs-1:1.1.1k-2.el7.x86_64
  file /usr/lib64/libcrypto.so.1.1.1k from install of openssl-libs-1:1.1.1k-5.el8_5.x86_64 conflicts with file from package openssl11-libs-1:1.1.1k-2.el7.x86_64
  file /usr/lib64/libssl.so.1.1.1k from install of openssl-libs-1:1.1.1k-5.el8_5.x86_64 conflicts with file from package openssl11-libs-1:1.1.1k-2.el7.x86_64



============================================================
                       END OF ERRORS                        
============================================================

How do I go further?
Thanks
Gianni

2

The first two messages give away a problem:

Failed to create directory /var/lib/leapp/el8userspace//sys/fs/selinux: Read-only file system

If the filesystem is read only, then leapp cannot create a directory! If it were me doing this that would be the first thing to fix, and then try again.

3

nah that’s a bogus error, sysfs is always going to be readonly its a virtual filesystem.

the real problem is that EPEL has been used and its packages not removed or repo disabled.

massive red bit on the wiki says:

DANGER

The ELevate project supports only CentOS repositories. It doesn’t support other external repositories. Please, check the ELevate Frequent Issues page for known and frequent issues.

4

I wonder how difficult would it be for the community to start adding metadata for EPEL, so people with packages from EPEL could migrate as well.
pes.almalinux.org might be helpful there

5

I know this is an older thread but I am one of those that has EPEL and other non-CentOS packages installed. The instructions for migrate says to uninstall them to make Leapp run w/o error but makes no mention about how or if you can re-install such packages. Persumably if one has these installed initially they will be needed post-migration. Any advise appreciated

6

That is always a question when in new distro. What in new distro yields the equivalent features than were in old distro and what is the most appropriate way to configure those?

The ELEvate does have (presumably, I have never used it) list of what was in CentOS 7 and what in EL8 distros is equivalent, and how to translate configs. What was in EPEL 7 and what is in EPEL 8 would be a long list.

You should know what you have in CentOS 7 and why. Then look up how to satisfy the ‘whys’ in EL8, like AlmaLinux 8, or are all those even relevant today?

7

Thanks for the response and the good information. This is actually a migration from COS 7 to ultimately Alma 9 following the Elevate page on that. So maybe I have to do this package question twice also going from Alma 8 to Alma 9 too. Most of the packages I use are pearl and mysql related and some denyhosts bits in there. I’ll look into more info on the various EPEL distros to see what crosses over. Again, thanks for the suggestions.