When rabbit is failing for a specific quorum queue, the only thing to
do is to delete the queue (as per rabbit doc, see [1]).
So, to avoid the RPC service to be broken until an operator eventually
do a manual fix on it, catch any INTERNAL ERROR (code 541) and trigger
the deletion of the failed queues under those conditions.
So on next queue declare (triggered from various retries), the queue
will be created again and the service will recover by itself.
Reviewed: https:/ /review. opendev. org/c/openstack /oslo.messaging /+/900891 /opendev. org/openstack/ oslo.messaging/ commit/ 34260a40358b179 80f151dd6f4c414 5533fba799
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.2
commit 34260a40358b179 80f151dd6f4c414 5533fba799
Author: Arnaud Morin <email address hidden>
Date: Fri Jul 21 16:51:51 2023 +0200
Auto-delete the failed quorum rabbit queues
When rabbit is failing for a specific quorum queue, the only thing to
do is to delete the queue (as per rabbit doc, see [1]).
So, to avoid the RPC service to be broken until an operator eventually
do a manual fix on it, catch any INTERNAL ERROR (code 541) and trigger
the deletion of the failed queues under those conditions.
So on next queue declare (triggered from various retries), the queue
will be created again and the service will recover by itself.
Closes-Bug: #2028384
Related-bug: #2031497
[1] https:/ /www.rabbitmq. com/quorum- queues. html#availabili ty
Signed-off-by: Arnaud Morin <email address hidden> 091a4e0bf23bb59 3aca89c5905 78ceb384063f81d b2e92a2ebd)
Change-Id: Ib8dba833542973
(cherry picked from commit 8e3c523fd74257a