View Issue Details

IDProjectCategoryView StatusLast Update
0000433AlmaLinux-8-OTHERpublic2024-05-15 18:19
Reporterholzman2 Assigned Toalukoshko  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Summary0000433: Issues with Scientific Linux 7 to alma8 migration
DescriptionI'm testing SL7 -> alma8 migration (with the goal of then migrating to alma9).

There are a number of issues:

Pre-upgrade:

The sl-logos package conflicts with almalinux-logos; I had to rpm -e to continue.

Post-upgrade:

almalinux-release is not installed. (I hacked around it by removing sl-release, manually setting /etc/os-release and /etc/redhat-release to look like Centos 8, running almalinux-deploy.sh, and mv'ing /etc/os-release.rpmnew to /etc/os-release).

A number of EL7 packages are still present, some of which will interfere with migration to alma9:
btrfs-progs-4.9.1-1.el7.x86_64
elevate-release-1.0-2.el7.noarch
kernel-3.10.0-1160.102.1.el7.x86_64
leapp-0.14.0-1.el7.noarch
leapp-data-almalinux-0.1-6.el7.noarch
leapp-upgrade-el7toel8-0.16.0-6.el7.elevate.17.noarch
python2-leapp-0.14.0-1.el7.noarch
sl7-upgrade-0.1.1-2.el7.noarch
yum-conf-extras-1.0-1.el7.noarch
yum-conf-repos-1.0-1.el7.noarch
yum-plugin-upgrade-helper-1.1.31-54.el7_8.noarch
sl-indexhtml
yum-conf-sl7x
sl-release-notes

sl-indexhtml would not uninstall cleanly, but can be removed with --nodeps and replaced with the almalinux-indexhtml package.

The /etc/yum.conf file still has:
exclude=python2-leapp,snactor,leapp-upgrade-el7toel8,leapp

Tagsalma8, elevate, leapp
abrt_hash
URL

Activities

jcpunk

2024-05-14 13:48

reporter   ~0001031

Scientific Linux Source packages typically come from a repo named : sl-source

jcpunk

2024-05-14 13:53

reporter   ~0001032

Packages without an almalinux equivalent:
sl-bookmarks
sl-release-notes
sl7-upgrade
yum-conf-sl7x
yum-conf-extras
yum-conf-repos
kmod-openafs-1.6-sl
kmod-openafs-1.6-sl-1062
kmod-openafs-1.6-sl-1127
kmod-openafs-1.6-sl-1160
kmod-openafs-1.6-sl-123
kmod-openafs-1.6-sl-229
kmod-openafs-1.6-sl-327
kmod-openafs-1.6-sl-514
kmod-openafs-1.6-sl-693
kmod-openafs-1.6-sl-862
kmod-openafs-1.6-sl-957
openafs-1.6-sl
openafs-1.6-sl-authlibs
openafs-1.6-sl-authlibs-devel
openafs-1.6-sl-client
openafs-1.6-sl-compat
openafs-1.6-sl-devel
openafs-1.6-sl-kernel-source
openafs-1.6-sl-kpasswd
openafs-1.6-sl-krb5
openafs-1.6-sl-module-tools
openafs-1.6-sl-plumbing-tools
openafs-1.6-sl-server


Packages to replace with their almalinux equivalent:
sl-indexhtml to almalinux-indexhtml
sl-logos to almalinux-logos
sl-release to almalinux-release

ykohut

2024-05-14 13:58

developer   ~0001033

Is that OK if all packages "without an almalinux equivalent" are removed ?
Especially openafs related ...

ykohut

2024-05-14 14:09

developer   ~0001034

Also, It is not required to know repository of "Scientific Linux Source packages".

For each package you listed above, please specify repository name (the package comes from).

jcpunk

2024-05-14 14:13

reporter   ~0001035

> Is that OK if all packages "without an almalinux equivalent" are removed ?

I'd expect them to be removed.

> For each package you listed above, please specify repository name (the package comes from).
Packages can come from one of the following repos:
sl
sl-security
sl-fastbugs
repos

jcpunk

2024-05-14 14:20

reporter   ~0001036

Some how this was submitted while I was still typing....

 yum-conf-extras comes from repos

yum-conf-repos can come from either sl or repos

The rest can come from any of:

sl
sl-security
sl-fastbugs

Pat

ykohut

2024-05-14 15:03

developer   ~0001037

Last edited: 2024-05-15 07:42

Matching package to the repository it comes from:

 sl-release-notes sl
 sl7-upgrade sl
 yum-conf-extras repos
 yum-conf-repos repos
 yum-plugin-upgrade-helper sl
 yum-conf-sl7x sl
 sl-bookmarks sl

 sl-indexhtml sl almalinux-indexhtml baseos
 sl-logos sl almalinux-logos appstream
 sl-release sl almalinux-release baseos

openafs-1.6-sl* sl
kmod-openafs-1.6-sl* sl

ykohut

2024-05-15 10:03

developer   ~0001038

Some updates related to the migration.

1. Adding some packages to pes-events.json allows SL migration.

2. The only issue occurs:
2024-05-14 19:36:13.393 DEBUG PID: 1021 leapp.workflow.RPMUpgrade.dnf_upgrade_transaction: error: unpacking of archive failed on file /usr/share/doc/redhat-release;664392c1: cpio: File from package already exists as a directory in system

The reason is the /usr/share/doc/redhat-release directory isn't owned by any SL package. So it remains in file-system even after all SL packages are removed, and conflicts with almalinux-release package, which tries to install it as file (symlink).

ykohut

2024-05-15 10:53

developer   ~0001039

The solution could be to update the sl-release package to own the /usr/share/doc/redhat-release directory.

The following patch can do the job:

--- /root/rpmbuild/SPECS/sl-release.spec 2020-10-05 18:30:07.000000000 +0300
+++ /root/rpmbuild/SPECS/sl-release.spec.patched 2024-05-15 11:39:33.978514508 +0300
@@ -4,7 +4,7 @@
 
 # increment this to get the stuff after the - higher
 # helps for making the rolling one go obsolete
-%define release_count 1
+%define release_count 2
 
 # Ok so we are 7.minor_release_version, what should
 # that value be?
@@ -421,6 +421,7 @@ fi
 /etc/pki/rpm-gpg/
 /etc/rpm/macros.dist
 %{_sysconfdir}/pki/secure-boot/
+%{_docdir}/redhat-release
 %{_docdir}/redhat-release/*
 %{_docdir}/%{name}
 %{_datadir}/redhat-release/*
@@ -452,6 +453,9 @@ fi
 
 ##################################################################
 %changelog
+* Wed May 15 2024 Yuriy Kohut <ykohut@almalinux.org> - 7.9-0.2
+- Include /usr/share/doc/redhat-release directory to the package
+
 * Wed Sep 30 2020 Pat Riehecky <riehecky@fnal.gov> - 7.9-0.1
 - Add new secure boot key
 - Bump for 7.9 BETA

Please let know if you are able to make such update to the sl-release package.

ykohut

2024-05-15 11:47

developer   ~0001041

The same is for /usr/share/redhat-release directory.

Updated patch will look like:
sl-release.spec.patch (1,100 bytes)   
--- /root/rpmbuild/SPECS/sl-release.spec.orig	2024-05-15 13:05:15.309661559 +0300
+++ /root/rpmbuild/SPECS/sl-release.spec	2020-10-05 18:30:07.000000000 +0300
@@ -4,7 +4,7 @@
 
 # increment this to get the stuff after the - higher
 #  helps for making the rolling one go obsolete
-%define release_count 2
+%define release_count 1
 
 # Ok so we are 7.minor_release_version, what should
 # that value be?
@@ -421,9 +421,9 @@ fi
 /etc/pki/rpm-gpg/
 /etc/rpm/macros.dist
 %{_sysconfdir}/pki/secure-boot/
-%{_docdir}/redhat-release
+%{_docdir}/redhat-release/*
 %{_docdir}/%{name}
-%{_datadir}/redhat-release
+%{_datadir}/redhat-release/*
 %{_datadir}/%{name}
 %{_prefix}/lib/systemd/system-preset/*
 /etc/pki/product-default
@@ -452,9 +452,6 @@ fi
 
 ##################################################################
 %changelog
-* Wed May 15 2024 Yuriy Kohut <ykohut@almalinux.org> - 7.9-0.2
-- Include /usr/share/doc/redhat-release and /usr/share/redhat-release directories to the package
-
 * Wed Sep 30 2020 Pat Riehecky <riehecky@fnal.gov> - 7.9-0.1
 - Add new secure boot key
 - Bump for 7.9 BETA
sl-release.spec.patch (1,100 bytes)   

ykohut

2024-05-15 12:05

developer   ~0001042

Also, the workaround could be removing of both directories prior to running the upgrade.

# rm -rf /usr/share/redhat-release /usr/share/doc/redhat-release
# leapp preupgrade
...

jcpunk

2024-05-15 13:09

reporter   ~0001043

For now the workaround is probably the way to go.

alukoshko

2024-05-15 14:36

administrator   ~0001044

ykohut, looks like your patch is reversed.

ykohut

2024-05-15 18:19

developer   ~0001045

I. The updated 'leapp-data-almalinux' package is available. It includes Scientific Linux specific data.

II. To do the migration, please use the instruction at https://wiki.almalinux.org/elevate/ELevating-CentOS7-to-AlmaLinux-9.html#migrate-centos-7-to-almalinux-8

Prior to the 'Install leapp packages and migration data for AlmaLinux:' step, you should:
1). Install 'elevate-testing' repository, run:
# curl -o /etc/yum.repos.d/elevate-testing.repo https://repo.almalinux.org/elevate/testing/elevate-testing.repo

2). Apply the workaround by running:
# rm -rf /usr/share/redhat-release /usr/share/doc/redhat-release

III. Follow the rest steps unchanged.

Issue History

Date Modified Username Field Change
2023-10-13 19:30 holzman2 New Issue
2023-10-13 20:37 holzman2 Tag Attached: alma8
2023-10-13 20:37 holzman2 Tag Attached: elevate
2023-10-13 20:37 holzman2 Tag Attached: leapp
2023-11-27 21:24 alukoshko Assigned To => alukoshko
2023-11-27 21:24 alukoshko Status new => assigned
2024-05-14 13:48 jcpunk Note Added: 0001031
2024-05-14 13:53 jcpunk Note Added: 0001032
2024-05-14 13:58 ykohut Note Added: 0001033
2024-05-14 14:09 ykohut Note Added: 0001034
2024-05-14 14:13 jcpunk Note Added: 0001035
2024-05-14 14:20 jcpunk Note Added: 0001036
2024-05-14 15:03 ykohut Note Added: 0001037
2024-05-15 07:35 ykohut Note Edited: 0001037
2024-05-15 07:42 ykohut Note Edited: 0001037
2024-05-15 10:03 ykohut Note Added: 0001038
2024-05-15 10:53 ykohut Note Added: 0001039
2024-05-15 11:47 ykohut Note Added: 0001041
2024-05-15 11:47 ykohut File Added: sl-release.spec.patch
2024-05-15 12:05 ykohut Note Added: 0001042
2024-05-15 13:09 jcpunk Note Added: 0001043
2024-05-15 14:36 alukoshko Note Added: 0001044
2024-05-15 18:19 ykohut Note Added: 0001045