Bug 1180864

Summary: multiprocessing BaseManager serve_client() does not check EINTR on recv
Product: Red Hat Enterprise Linux 6 Reporter: Dima Kuznetsov <dkuznets>
Component: pythonAssignee: Robert Kuska <rkuska>
Status: CLOSED ERRATA QA Contact: Branislav NĂ¡ter <bnater>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.5CC: bkabrda, bnater, danken, dkutalek, jberan, oourfali, rkuska
Target Milestone: rc   
Target Release: 6.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-2.6.6-56.el6 Doc Type: Bug Fix
Doc Text:
Cause: multiprocessing doesn't ignore EINTR Consequence: BaseManager class terminated unexpectedly when multiple signals were received on a same process Fix: multiprocessing module has been modified so that its methods ignore the "interrupted function" (EINTR) Result: BaseManager class doesn't terminate unexpectedly when multiple signals were received on a same process
Story Points: ---
Clone Of:
: 1181624 (view as bug list) Environment:
Last Closed: 2015-07-22 06:39:59 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:
Bug Depends On: 1181624    
Bug Blocks: 841486    

Description Dima Kuznetsov 2015-01-11 10:32:56 UTC
Description of problem:
There is a problem with using BaseManager and receiving signals on the same process, there was a bug opened on python [1] and it was fixed for 2.7 and 3.x.
We're using BaseManager and rely on signals on el6, can this be backported to python2.6?

[1] - http://bugs.python.org/issue17097

Version-Release number of selected component (if applicable):
python2.6

How reproducible:
100%

Steps to Reproduce:
1. Included in the python bug [1]

Comment 2 Bohuslav "Slavek" Kabrda 2015-01-12 10:13:12 UTC
Yes, we can fix this for 6.7, using the patch provided in the linked upstream issue [1] is the way to go.

[1] https://hg.python.org/cpython/rev/bc34fe4a0d58

Comment 5 errata-xmlrpc 2015-07-22 06:39:59 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, 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://rhn.redhat.com/errata/RHSA-2015-1330.html