Bug 1208994

Summary: Backported fix for 'maximum recursion depth exceeded in GreenSocket.__del__'
Product: [Fedora] Fedora Reporter: Josh McSavaney <mcsaucy>
Component: python-eventletAssignee: Lev Shamardin <shamardin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 20CC: apevec, kevin, mcsaucy, p, shamardin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:19:16 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:
Attachments:
Description Flags
Tarball of proposed changes none

Description Josh McSavaney 2015-04-04 23:22:00 UTC 
Created attachment 1010986 [details]
Tarball of proposed changes

BLUF: I've backported python-eventlet patches from v0.16 to v0.15.2 that correct a destructor triggering a max recursion depth exception.

GH-137 (https://github.com/eventlet/eventlet/issues/137) for upstream addresses an issue where a GreenSocket object's destructor could trigger an infinite recursion scenario under certain circumstances. I've seen this behavior crop up with a few Openstack components, where it has masked other problems and filled logs with remarkable speed.

Now, this issue has been corrected in v0.16, but v0.16 also saw the removal of then-deprecated API elements. Rather than risking degradation of support for python-eventlet's dependents by upgrading to a newer version, I'm advocating for a bugfix release that includes the patch required to fix the issue (plus 2 additional patches to support the backport).

I've attached a tarball containing the required patches and specfile changes.

Thanks,

-J
Comment 1 Fedora End Of Life 2015-05-29 13:46:53 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2015-06-30 00:19:16 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.