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.
Bug 1990421 - RHEL 8 python39* packages conflict with python3 packages from RHEL 9 during a LEAPP upgrade
Summary: RHEL 8 python39* packages conflict with python3 packages from RHEL 9 during a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: python-rpm-generators
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Tomas Orsava
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On:
Blocks: 2055693 2058297 2058298 2058301 2058302 2058303 2058304 2058305 2058307 2058309 2058311 2058312 2058313 2058314 2058315 2058316 2058317 2058318 2058319 2058322 2058323 2058324 2058325 2058326 2058327 2058328 2058329 2058330
TreeView+ depends on / blocked
 
Reported: 2021-08-05 11:15 UTC by Tomas Orsava
Modified: 2022-05-17 13:52 UTC (History)
4 users (show)

Fixed In Version: python-rpm-macros-3.9-49.el9 python-rpm-generators-12-8.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2055693 (view as bug list)
Environment:
Last Closed: 2022-05-17 13:52:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
LEAPP error log (648.37 KB, text/plain)
2021-08-05 11:16 UTC, Tomas Orsava 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-92498 0 None None None 2021-08-05 12:00:19 UTC
Red Hat Product Errata RHBA-2022:2606 0 None None None 2022-05-17 13:52:49 UTC

Description Tomas Orsava 2021-08-05 11:15:05 UTC 
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
Comment 1 Tomas Orsava 2021-08-05 11:16:12 UTC 
Created attachment 1811186 [details]
LEAPP error log
Comment 2 Miro Hrončok 2021-08-05 11:27:11 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.
Comment 3 Tomas Orsava 2021-08-05 11:46:01 UTC 
(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 4 Petr 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.
Comment 5 Tomas Orsava 2021-11-24 09:46:06 UTC 
(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.
Comment 6 Tomas Orsava 2021-12-01 15:35:57 UTC 
> 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.
Comment 22 errata-xmlrpc 2022-05-17 13:52:36 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.