Bug 1105094

Summary: neutron-server gets stuck in poll python-qpid 0.18
Product: Red Hat Enterprise MRG Reporter: Petr Matousek <pematous>
Component: python-qpidAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED ERRATA QA Contact: Petr Matousek <pematous>
Severity: high Docs Contact:
Priority: high    
Version: DevelopmentCC: acathrow, esammons, freznice, jross, kgiusti, lbezdick, lzhaldyb, mburns, mcressma, mwagner, pematous, tross
Target Milestone: 2.5.1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-qpid-0.18-12 Doc Type: Bug Fix
Doc Text:
Previously, the neutron messaging client rewrote (by method of "monkey-patching") the python selector module to support eventlet threading. The rewritten client did not update select.poll() during this process, which is used by qpid-python to manage I/O. This resulted in poll() deadlocks and neutron server hangs. The fix introduces updates to the qpid-python library that avoid calling poll() if eventlet threading is detected. Instead, the eventlet-aware select() is called, which prevents deadlocks from occurring and corrects the originally reported issue.
Story Points: ---
Clone Of: 1102040 Environment:
Last Closed: 2014-06-30 10:26:30 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: 1102040, 1108005, 1109079, 1112372, 1143749    
Bug Blocks:    

Comment 4 Petr Matousek 2014-06-16 17:26:45 UTC
This issue is fixed with python-qpid-0.18-12.el6

# neutron net-list --format=csv --column=id --quote=none
id
508fabf2-ce48-4258-b674-5346d4d6afb0
328de1c7-7569-4b87-8ea8-9ba2979ee76a

Packstack installation was successful without any issues.

Note: skipping test for python-qpid.el5 due to lack of rhel-osp5 support on rhel5.

-> VERIFIED

Comment 7 errata-xmlrpc 2014-06-30 10:26:30 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.

http://rhn.redhat.com/errata/RHBA-2014-0804.html