Bug 2127920

Summary:	Removing leapp* packages after the upgrade keeps untracked pyc files [rhel-8]
Product:	Red Hat Enterprise Linux 8	Reporter:	Petr Stodulka <pstodulk>
Component:	leapp-repository	Assignee:	Petr Stodulka <pstodulk>
Status:	CLOSED ERRATA	QA Contact:	Martin Klusoň <mkluson>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	mmacura
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	leapp-repository-0.18.0-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-16 08:37:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Stodulka 2022-09-19 11:39:34 UTC

This bug was initially created as a copy of Bug #2127918

I am copying this bug because: 



After the in-place upgrade, the removal of "*leapp*" packages keep many untracked *pyc files present on the disk.

    /usr/lib/python2.7/site-packages/leapp/**cpython36.pyc
    /usr/share/leapp-repository/**cpython36.pyc

Expected result:
Removal of "*leapp*" and snactor packages after the IPU does not leave many untracked "pyc" files on the system.

Additional info:
These files are not removed by dnf automatically as they are part of the rpm. That's happening because these files are created after the upgrade rpm transaction, whenwe execute `leapp` with the new python which creates all new `pyc` files.

Possibly we could fix that by running the python with `-B` option or using `PYTHONDONTWRITEBYTECODE` envar.

Comment 6 errata-xmlrpc 2023-05-16 08:37:40 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 (leapp-repository bug fix and enhancement update), 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-2023:2839