Python36.el7 rpms conflicts with python3.el8 rpms

Rocky Linux General
1

Hi

We are migrating centos centos 7.9 to rocky Linux 8.7. We have ceph octopus with python36…-el7.rpms in centos7.9 as dependencies, while migrating to Rocky Linux python3…-el8 rpms conflicts with this python36…-el7 rpms. We need your support to identify this issue.

Leapp log file,

file /usr/lib/python3.6/site-packages/requests/api.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/auth.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/certs.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/compat.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/cookies.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/exceptions.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/hooks.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/models.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/sessions.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/status_codes.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/structures.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/requests/utils.py from install of python3-requests-2.20.0-2.1.el8_1.noarch conflicts with file from package python36-requests-2.14.2-2.el7.noarch
file /usr/lib/python3.6/site-packages/pycache/prettytable.cpython-36.opt-1.pyc from install of python3-prettytable-0.7.2-14.el8.noarch conflicts with file from package python36-prettytable-0.7.2-19.el7.noarch
file /usr/lib/python3.6/site-packages/pycache/prettytable.cpython-36.pyc from install of python3-prettytable-0.7.2-14.el8.noarch conflicts with file from package python36-prettytable-0.7.2-19.el7.noarch
file /usr/lib/python3.6/site-packages/prettytable.py from install of python3-prettytable-0.7.2-14.el8.noarch conflicts with file from package python36-prettytable-0.7.2-19.el7.noarch
file /usr/lib/python3.6/site-packages/pycache/ceph_argparse.cpython-36.opt-1.pyc from install of ceph-common-1:12.2.7-9.el8.x86_64 conflicts with file from package python3-ceph-argparse-2:15.2.17-0.el7.x86_64

Regards
Velmurugan.

2

ill take a stab at this as it seems obvious.
each version of the Rhel derived distributions upgrades the base python version , as it does all packages.
you are trying to move an app that has a dependency on a specific version of python to a new OS version.
the app may work with the new version of python, as long as there is no dependency on specific modules, but in the case “may comes with a touch of hope”.
in other words it may not work.
or if it does it may not be supported if you have a vendor contract.
so you have a couple of options.
install some kind of chroot around your app which has the older version of python libraries.
or stay with the older version of OS until your app is supported on the newer version of python.

to answer your next question if you dont know what chrooting an app is, its putting a fake environment around it, where what it sees as root, actually starts somewhere else, ie /home/app/root.
everything it sees from that perspective is provided within the chroot tree.
chroot is provided by coreutils.

oh and finaly you should have checked the Installing Ceph — Ceph Documentation

ceph-deploy is not actively maintained. It is not tested on versions of Ceph newer than Nautilus. It does not support RHEL8, CentOS 8, or newer operating systems.

regards peter