[AMQP 1.0] Re-transmit messages that are returned by the message bus

[Ken Giusti]

The dispatch router may refuse to forward a sent message due to a topology change. In this case it will return the message back to the sender so it may be re-sent at a later point.

This is similar to a requeue() operation, but for a brokerless backend.

When a message is returned to the amqp1 driver and its terminal disposition is "RELEASED" the driver should attempt to re-deliver the message if the 'retry' parameter to the send call allows it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/407681

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/407681
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=9fab0bdbc8d9309de28a18ed4f167b8abccb765f
Submitter: Jenkins
Branch: master

commit 9fab0bdbc8d9309de28a18ed4f167b8abccb765f
Author: Kenneth Giusti <email address hidden>
Date: Mon Dec 5 08:46:43 2016 -0500

    [AMQP 1.0] Resend messages that are released or modified

    A message ack status of 'RELEASED' or 'MODIFIED' indicates that the
    message was not accepted by the destination due to some temporary
    issue. These status are used to indicate to the sender that the
    message can be safely re-transmitted without risk of duplication
    (i.e. the delivery is not 'in-doubt'). For example this may happen
    during a message bus topology update if a message is sent before the
    topology stabilizes.

    This change implements re-send for these cases.

    Closes-Bug: #1646586
    Change-Id: I419e23b59e3eb90fda3f1c0e7ddf54ef98870e4b

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/oslo.messaging 5.17.0 release.