Bug 1175872
Summary: | [RHEL 6]neutron-server gets stuck in poll python-qpid 0.22 | |||
---|---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Irina Boverman <iboverma> | |
Component: | python-qpid | Assignee: | Irina Boverman <iboverma> | |
Status: | CLOSED ERRATA | QA Contact: | Messaging QE <messaging-qe-bugs> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 3.0 | CC: | acathrow, esammons, freznice, iboverma, jross, kgiusti, lbezdick, lhh, mburns, mcressma, messaging-qe-bugs, mwagner, pematous, sgraf, tfreger, tross | |
Target Milestone: | 3.0.2 | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | python-qpid-0.22-19 | 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: | 1143749 | |||
: | 1175882 (view as bug list) | Environment: | ||
Last Closed: | 2015-03-19 17:10:32 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: | ||||
Bug Blocks: | 1175882, 1193218 |
Comment 3
Toni Freger
2015-01-18 13:48:40 UTC
This issue is not applicable to the earlier versions of RHEL OSP. The fix was included in this release of MRG Messaging and sanity testing; regression testing here and el7 versions of this fix were in fact verified. 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-0707.html |