Bump amqp requirement version to >=2.4.1

Bumping the version of amqp in requirements.txt and
lower-constraints.txt from 2.4.0 to 2.4.1 to mitigate issues with
MessagingTimeouts when using TLS due to a amqp bug that was fixed in
2.4.1

Change-Id: I0b094f32dec24c70f95ccd509164a14a71fcfc7d
Closes-Bug: #1800957
This commit is contained in:
mb 2019-02-18 17:16:58 +01:00
parent 0a784d2604
commit 64f74cd2cc
3 changed files with 18 additions and 2 deletions

View File

@ -1,5 +1,5 @@
alabaster==0.7.10
amqp==2.4.0
amqp==2.4.1
appdirs==1.3.0
Babel==2.3.4
bandit==1.1.0

View File

@ -0,0 +1,16 @@
---
critical:
- |
In combination with amqp<=2.4.0, ``oslo.messaging`` was unreliable
when configured with TLS (as is generally recommended). Users would
see frequent errors such as this::
MessagingTimeout: Timed out waiting for a reply to message ID ae039d1695984addbfaaef032ce4fda3
Such issues would typically lead to downstream service timeouts,
with no recourse available other than disabling TLS altogether
(see `bug 1800957
<https://bugs.launchpad.net/oslo.messaging/+bug/1800957>`_).
The underlying issue is fixed in amqp version 2.4.1, which is now
the minimum version that ``oslo.messaging`` requires.

View File

@ -26,7 +26,7 @@ PyYAML>=3.12 # MIT
# rabbit driver is the default
# we set the amqp version to ensure heartbeat works
amqp>=2.4.0 # BSD
amqp>=2.4.1 # BSD
kombu!=4.0.2,>=4.0.0 # BSD
# middleware