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.
Comment 2Charalampos Stratakis
2018-09-17 17:50:47 UTC
If I recall correctly we didn't backport this patch to RHEL7 due to concerns with backwards compatibility. Petr could you confirm that?
Comment 3Petr Viktorin (pviktori)
2018-09-18 09:10:04 UTC
Charris: no, this is a different issue than what you're thinking about. This one is not invasive.
The change adds error checking for the case when source for a Python module cannot be read (for example, on an unreliable networked filesystem).
Previously, this did not raise an error, but resulted in an empty bytecode cache file. The module can not be imported until the cache file is manually removed.
With the change, such compilation fails with an exception. This allows the user to detect the issue as it happens.
Note that while I'm sure the upstream patch is an improvement, I haven't checked if it addresses all instances of the issue. How important is this to the customer?
Also, testing this will be rather involved. As noted in the upstream issue, reliably reproducing the issue "involves LD_PRELOADing an dynamic library which hooks __srget".
Comment 4Petr Viktorin (pviktori)
2018-09-20 12:51:40 UTC
I set the wrong needinfo. Paulo, can you answer the following?
> Note that while I'm sure the upstream patch is an improvement, I haven't checked if it addresses all instances of the issue. How important is this to the customer?
Also, it is probably too late now to backport this to RHEL 6 (Python 2.6).
Comment 10Petr Viktorin (pviktori)
2018-10-22 09:19:06 UTC
Bug #1629982 tracks this for RHEL 7.
*** This bug has been marked as a duplicate of bug 1629982 ***