Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1427792 - RabbitMQ: Bad address when CONFIG_AMQP_ENABLE_SSL=y
RabbitMQ: Bad address when CONFIG_AMQP_ENABLE_SSL=y
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-oslo-messaging (Show other bugs)
11.0 (Ocata)
Unspecified Unspecified
high Severity high
: rc
: 11.0 (Ocata)
Assigned To: Victor Stinner
Asaf Hirshberg
: Triaged, ZStream
Depends On: 1423593
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-01 04:00 EST by Victor Stinner
Modified: 2018-01-16 07:24 EST (History)
18 users (show)

See Also:
Fixed In Version: python-oslo-messaging-5.17.1-2.el7ost
Doc Type: Bug Fix
Doc Text:
The Remote Procedure Call (RPC) message acknowledgement in Oslo Messaging was not thread-safe. Consequently, a race condition caused an RPC timeout in Ceilometer. The message acknowledgement in Oslo Messaging has been fixed. Now, Ceilometer responds correctly.
Story Points: ---
Clone Of: 1423593
Environment:
Last Closed: 2017-05-17 16:03:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 440205 None None None 2017-03-13 05:49 EDT
Red Hat Product Errata RHEA-2017:1245 normal SHIPPED_LIVE Red Hat OpenStack Platform 11.0 Bug Fix and Enhancement Advisory 2017-05-17 19:01:50 EDT

  None (edit)
Comment 2 Victor Stinner 2017-03-13 10:06:13 EDT
python-oslo-messaging-5.17.1-2.el7ost contains the "rabbit: make ack/requeue thread-safe" and is now ready for tests ;-)
Comment 4 Asaf Hirshberg 2017-03-27 01:51:08 EDT
Code Verified.
Comment 8 errata-xmlrpc 2017-05-17 16:03:01 EDT
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/RHEA-2017:1245

Note You need to log in before you can comment on or make changes to this bug.