8e3c523fd7
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#availability Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com> Change-Id: Ib8dba833542973091a4e0bf23bb593aca89c5905
Team and repository tags
Oslo Messaging Library
The Oslo messaging API supports RPC and notifications over a number of different messaging transports.
- License: Apache License, Version 2.0
- Documentation: https://docs.openstack.org/oslo.messaging/latest/
- Source: https://opendev.org/openstack/oslo.messaging
- Bugs: https://bugs.launchpad.net/oslo.messaging
- Release notes: https://docs.openstack.org/releasenotes/oslo.messaging/