After reviewing a response from RabbitMQ and some important bits of their docs (see the Queue Properties section last paragraph) https://www.rabbitmq.com/docs/queues#properties, it looks like this is the result of an expected race condition. Whilst their docs don't explicitly call out this case, it's so similar I expect it's the same issue.
My intention is to try switching our reply queues into HA mode, which both OSA and Kolla currently appear to exclude (^(?!(amq\.)|(.*_fanout_)|(reply_)).*). Given the response from RabbitMQ (see the discussion in https://github.com/rabbitmq/rabbitmq-server/discussions/11001), unless server-named exclusive queues are used, the current model (non-exclusive, classic) won't be supported in the future anyway. As such the options seem to be either use HA for reply queues, or switch to using quorum queues.
After reviewing a response from RabbitMQ and some important bits of their docs (see the Queue Properties section last paragraph) https:/ /www.rabbitmq. com/docs/ queues# properties, it looks like this is the result of an expected race condition. Whilst their docs don't explicitly call out this case, it's so similar I expect it's the same issue.
My intention is to try switching our reply queues into HA mode, which both OSA and Kolla currently appear to exclude (^(?!(amq\ .)|(.*_ fanout_ )|(reply_ )).*). Given the response from RabbitMQ (see the discussion in https:/ /github. com/rabbitmq/ rabbitmq- server/ discussions/ 11001), unless server-named exclusive queues are used, the current model (non-exclusive, classic) won't be supported in the future anyway. As such the options seem to be either use HA for reply queues, or switch to using quorum queues.