Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When upgrading from RHEL 8 to RHEL 9 using LEAPP, the upgrade fails if python39 packages were installed on the RHEL 8 system. The error says:
file /usr/lib/python3.9/site-packages/__pycache__/six.cpython-39.opt-1.pyc from install of python3-six-1.15.0-6.el9.noarch conflicts with file from package python39-six-1.15.0-3.module+el8.4.0+9822+20bf1249.noarch
<snip>
Full errer logfile attached.
How reproducible:
Every time
Steps to Reproduce:
1. Upgrade RHEL 8 to RHEL 9 using LEAPP, for example using this vagrant box: https://gitlab.cee.redhat.com/leapp/oamg-rhel8-vagrant
Actual results:
file /usr/lib/python3.9/site-packages/__pycache__/six.cpython-39.opt-1.pyc from install of python3-six-1.15.0-6.el9.noarch conflicts with file from package python39-six-1.15.0-3.module+el8.4.0+9822+20bf1249.noarch
<snip>
Full errer logfile attached.
Expected results:
System upgraded successfully
The python3-foo packages could automatically obsolete python39-foo packages. All we need is to adapt the https://gitlab.com/redhat/centos-stream/rpms/python-rpm-generators/-/blob/c9s/pythonname.attr generator to also have a %__pythonname_obsoletes macro. usual technical limits apply: packages without files and packages that have been renamed will need to maintain manual Obsoletes.
(In reply to Miro Hrončok from comment #2)
> The python3-foo packages could automatically obsolete python39-foo packages.
> All we need is to adapt the
> https://gitlab.com/redhat/centos-stream/rpms/python-rpm-generators/-/blob/
> c9s/pythonname.attr generator to also have a %__pythonname_obsoletes macro.
> usual technical limits apply: packages without files and packages that have
> been renamed will need to maintain manual Obsoletes.
Indeed, that's one possible solution.
Another possibility is that when we add definitions into the Package Evolution Service (PES) that python39-foo in RHEL 8 is named python3-foo in RHEL 9, LEAPP will correctly deal with the packages.
We can implement both solutions to be sure.
Comment 4Petr Viktorin (pviktori)
2021-08-11 12:28:27 UTC
> The python3-foo packages could automatically obsolete python39-foo packages. All we need is to adapt the https://gitlab.com/redhat/centos-stream/rpms/python-rpm-generators/-/blob/c9s/pythonname.attr generator to also have a %__pythonname_obsoletes macro. usual technical limits apply: packages without files and packages that have been renamed will need to maintain manual Obsoletes.
This looks like it's the best way to go. We should discuss on python-devel in Fedora.
(In reply to Tomas Orsava from comment #3)
> (In reply to Miro Hrončok from comment #2)
> > The python3-foo packages could automatically obsolete python39-foo packages.
> > All we need is to adapt the
> > https://gitlab.com/redhat/centos-stream/rpms/python-rpm-generators/-/blob/
> > c9s/pythonname.attr generator to also have a %__pythonname_obsoletes macro.
> > usual technical limits apply: packages without files and packages that have
> > been renamed will need to maintain manual Obsoletes.
>
> Indeed, that's one possible solution.
>
> Another possibility is that when we add definitions into the Package
> Evolution Service (PES) that python39-foo in RHEL 8 is named python3-foo in
> RHEL 9, LEAPP will correctly deal with the packages.
While testing this solution, I've found a bug in LEAPP: https://issues.redhat.com/browse/OAMG-6084>
> We can implement both solutions to be sure.
> While testing this solution, I've found a bug in LEAPP:
> https://issues.redhat.com/browse/OAMG-6084
LEAPP have a working patch that solves the bug and in effect resolves this upgrade problem.
In the meantime, in Fedora I'm verifying a second solution that automatically generates Obsoletes tags, if it works, I'll implement it in RHEL 9 as well.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (new packages: python-rpm-generators), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2606
Description of problem: When upgrading from RHEL 8 to RHEL 9 using LEAPP, the upgrade fails if python39 packages were installed on the RHEL 8 system. The error says: file /usr/lib/python3.9/site-packages/__pycache__/six.cpython-39.opt-1.pyc from install of python3-six-1.15.0-6.el9.noarch conflicts with file from package python39-six-1.15.0-3.module+el8.4.0+9822+20bf1249.noarch <snip> Full errer logfile attached. How reproducible: Every time Steps to Reproduce: 1. Upgrade RHEL 8 to RHEL 9 using LEAPP, for example using this vagrant box: https://gitlab.cee.redhat.com/leapp/oamg-rhel8-vagrant Actual results: file /usr/lib/python3.9/site-packages/__pycache__/six.cpython-39.opt-1.pyc from install of python3-six-1.15.0-6.el9.noarch conflicts with file from package python39-six-1.15.0-3.module+el8.4.0+9822+20bf1249.noarch <snip> Full errer logfile attached. Expected results: System upgraded successfully