Comment 5 for bug 1441298

@sileht, @dims,

This great patch is not in my oslo.messaging version but I should note that this issue has a different syndromes
Exceptions "Not found" raised by the consumer, not by the publisher

Like this
<179>Jan 29 13:04:45 node-2 nova-conductor Failed to consume message from queue: Basic.consume: (404) NOT_FOUND - no queue 'reply_cfeb6683351949ecae09082f682b15c9

So, after this exception ReplyWaiter dies

I saw this error on the different environments and it seems this particular issue does not related to rabbit cluster restarting as I have thought before

I think ReplyWaiter should retry to consume until timeout even if queue not found during firsts attempts