Debian Codegraph @

releasenotes/notes/agent-notification-auto-delete-queues-a3782fbeea2b57b1.yaml

raw
1 ---
2 upgrade:
3 - |
4 To fix `bug: 2004933 <https://storyboard.openstack.org/#!/story/2004933>`_
5 oslo.messaging notification queues are now renamed and created with
6 ``amqp_auto_delete=true``. When upgrading the agent old queues should be
7 deleted to free up message broker resources. Previous queue that can be
8 deleted are named ``ironic-neutron-agent-heartbeat.info``. There may
9 also be queues with uuid of previous agent instances as name, these can
10 also safely be deleted. (Look in the agent logs for relevant agent uuids).
11
12 On rabbitmq queues can be deleted via the web console. For example with
13 curl::
14
15 curl -i -u username:password \
16 -H "content-type:application/json" -XDELETE \
17 http://<host>:<web-port>/api/queues/<vhost>/<queue-name>
18
19 Another example with vhost: '/' deleting the
20 ironic-neutron-agent-heartbeat.info queue::
21
22 curl -i -u username:password \
23 -H "content-type:application/json" \
24 -XDELETE \
25 http://172.20.0.1:15672/api/queues/%2F/ironic-neutron-agent-heartbeat.info
26
27 .. Note:: In the example above the vhost is ``/``.
28 To ensure the vhost is correctly encoded the use of ``%2F``,
29 instead of ``/`` is required.
30 fixes:
31 - |
32 Fixes an issue where old oslo.messaging notification pool queues remained
33 in the broker without any consumer after agent restart. The notification
34 queues will now be created with ``amqp_auto_delete=true``. See `bug:
35 2004933 <https://storyboard.openstack.org/#!/story/2004933>`_.
36