This PR adds the ability for charms to set an expiry policy on queues:
https://opendev.org/openstack/charm-rabbitmq-server/commit/707fa0e093af3b6ab636b65b018c29049f7a51ff
This is especially useful for heat, where restating the service will leave behind old queues, making the count grow considerably over time. However, the pattern used is enclosed in double quotes, and rabbitmq treats the quotes as part of the pattern, which means it will never match. Here is the policy created in rabbitmq:
# rabbitmqctl list_policies -p openstack
Listing policies for vhost "openstack" ...
vhost name pattern apply-to definition priority
openstack HA ^(?!amq\.).* all {"ha-mode":"all","ha-sync-mode":"automatic"} 0
openstack heat_expiry "heat-engine-listener|engine_worker" queues {"expires":3600000} 1
openstack TTL ^(versioned_)?notifications.* queues {"message-ttl":3600000} 1
Notice the quotes surrounding the pattern:
"heat-engine-listener|engine_worker"
The following diff, makes it work as intended:
diff --git a/hooks/rabbit_utils.py b/hooks/rabbit_utils.py
index f1594c5..be8968a 100644
--- a/hooks/rabbit_utils.py
+++ b/hooks/rabbit_utils.py
@@ -443,7 +443,7 @@ def configure_ttl(vhost, ttlname, ttlreg, ttl):
return
rabbitmqctl('set_policy',
'{ttlname}'.format(ttlname=ttlname),
- '"{ttlreg}"'.format(ttlreg=ttlreg),
+ '{ttlreg}'.format(ttlreg=ttlreg),
'{{"expires":{ttl}}}'.format(ttl=ttl),
'--priority', '1',
'--apply-to', 'queues',
confirmed problem exists on master branch and that this change fixes it