File: bump-amqp-version-due-to-tls-issue-e877b152eb101c15.yaml

package info (click to toggle)
python-oslo.messaging 16.1.0-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,584 kB
  • sloc: python: 12,035; sh: 62; makefile: 24
file content (16 lines) | stat: -rw-r--r-- 657 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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.