Tested successfully on devstack. Would this be safe on production?
FYI :
The faulty queues seem to be declared somewhere around
here: https://github.com/openstack/heat/blob/master/heat/engine/service.py#L267
and here: https://github.com/openstack/heat/blob/master/heat/rpc/listener_client.py#L37
But I can be wrong because I can't find how to manage queues at all with oslo_messaging, and discovered that I fail to propose any heat fix because of oslo_messaging's documentation... After 3 days trying oslo_messaging's documentation I admit my total and absolute failure in understanding it... while I understood pika and rabbitmq in a few hours even though I never ever used them at all before...
In fact oslo_messaging doc looks more like a reminder for those who already know it but is unaccessible for new commers.
I would totally agree if told that this bug is a side effect of a faulty oslo_messaging doc...
Unless I have the wrong doc : https://wiki.openstack.org/wiki/Oslo/Messaging
Here is a quick workaround to automatically delete the idle queues without stopping heat services:
https:/ /gist.github. com/ygbourhis/ 8d258ae76d62ef1 1a2f77f0251c906 ff
Tested successfully on devstack. Would this be safe on production?
FYI : /github. com/openstack/ heat/blob/ master/ heat/engine/ service. py#L267 /github. com/openstack/ heat/blob/ master/ heat/rpc/ listener_ client. py#L37 /wiki.openstack .org/wiki/ Oslo/Messaging
The faulty queues seem to be declared somewhere around
here: https:/
and here: https:/
But I can be wrong because I can't find how to manage queues at all with oslo_messaging, and discovered that I fail to propose any heat fix because of oslo_messaging's documentation... After 3 days trying oslo_messaging's documentation I admit my total and absolute failure in understanding it... while I understood pika and rabbitmq in a few hours even though I never ever used them at all before...
In fact oslo_messaging doc looks more like a reminder for those who already know it but is unaccessible for new commers.
I would totally agree if told that this bug is a side effect of a faulty oslo_messaging doc...
Unless I have the wrong doc : https:/