From 3113175443b975d72699b3bbe6fea488c414a3ef Mon Sep 17 00:00:00 2001
From: Kenneth Giusti <kgiusti@gmail.com>
Date: Fri, 22 Feb 2019 12:50:14 -0500
Subject: [PATCH] Add release note for amqp library TLS/SSL error

Change-Id: I90c172d673084ff0cb0a3dd0fae21a5d62d35286
Related-Bug: #1800957
---
 .../notes/amqp-tls-issue-57c7f6ea894e03d7.yaml  | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 releasenotes/notes/amqp-tls-issue-57c7f6ea894e03d7.yaml

diff --git a/releasenotes/notes/amqp-tls-issue-57c7f6ea894e03d7.yaml b/releasenotes/notes/amqp-tls-issue-57c7f6ea894e03d7.yaml
new file mode 100644
index 000000000..213d5e23e
--- /dev/null
+++ b/releasenotes/notes/amqp-tls-issue-57c7f6ea894e03d7.yaml
@@ -0,0 +1,17 @@
+---
+issues:
+  - |
+    A bug in the ``amqp`` python library can cause the connection to the
+    RabbitMQ broker to hang when using SSL/TLS. This results in
+    frequent errors such as this::
+
+      MessagingTimeout: Timed out waiting for a reply to message ID ae039d1695984addbfaaef032ce4fda3
+
+    (see `bug 1800957
+    <https://bugs.launchpad.net/oslo.messaging/+bug/1800957>`_).
+
+    This bug has been fixed in `v2.4.1 of amqp
+    <https://github.com/celery/py-amqp/commit/bf122a05a21a8cc5bca314b0979f32c8026fc66e>`_.
+
+    It is recommended that deployments using SSL/TLS upgrade the amqp
+    library to v2.4.1 or later.