Bug 1741267
Summary: | heartbeats missed and connection timeout | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Hervé Beraud <hberaud> |
Component: | python-amqp | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED ERRATA | QA Contact: | pkomarov |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 14.0 (Rocky) | CC: | apevec, lhh, nlevinki, pkomarov, rheslop, rhos-maint |
Target Milestone: | z8 | Keywords: | Triaged, ZStream |
Target Release: | 14.0 (Rocky) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-amqp-2.3.2-4.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, SSLError timeoutes were not handled properly; socket.timeout() was not raised. This could cause rabbitmq driver connections to lockup. This patch ensures SSLError timeouts are treated as socket timeouts so that oslo.messaging and services log errors related to rabbitmq heartbeat and that the connection between service and the rabbitmq server remains stable.
|
Story Points: | --- |
Clone Of: | 1740681 | Environment: | |
Last Closed: | 2019-11-06 16:53:57 UTC | Type: | --- |
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: | 1740681 | ||
Bug Blocks: |
Description
Hervé Beraud
2019-08-14 15:59:55 UTC
python-amqp-2.3.2-4.el7ost Verified , (undercloud) [stack@undercloud-0 ~]$ rhos-release -L Installed repositories (rhel-7.7): 14 ceph-3 ceph-osd-3 rhel-7.7 (undercloud) [stack@undercloud-0 ~]$ cat core_puddle_version 2019-10-21.1(undercloud) [stack@undercloud-0 ~]$ rpm -qa | grep amqp python2-amqp-2.3.2-5.el7ost.noarch (undercloud) [stack@undercloud-0 ~]$ rpm -q --changelog python2-amqp-2.3.2-5.el7ost.noarch|grep SSL - Always treat SSLError timeouts as socket timeouts (#247) (rhbz#1741267) 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://access.redhat.com/errata/RHBA-2019:3747 |