Upgrade Notes¶

• To fixbug: 2004933oslo.messaging notification queues are now renamed and created withamqp_auto_delete=true. When upgrading the agent old queues should bedeleted to free up message broker resources. Previous queue that can bedeleted are namedironic-neutron-agent-heartbeat.info. There mayalso be queues with uuid of previous agent instances as name, these canalso safely be deleted. (Look in the agent logs for relevant agent uuids).

  On rabbitmq queues can be deleted via the web console. For example withcurl:

  curl-i-uusername:password \-H"content-type:application/json"-XDELETE \http://<host>:<web-port>/api/queues/<vhost>/<queue-name>

  Another example with vhost: ‘/’ deleting theironic-neutron-agent-heartbeat.info queue:

  curl-i-uusername:password \-H"content-type:application/json" \-XDELETE \http://172.20.0.1:15672/api/queues/%2F/ironic-neutron-agent-heartbeat.info

  Note

  In the example above the vhost is/.To ensure the vhost is correctly encoded the use of%2F,instead of/ is required.

Bug Fixes¶

• Fixes an issue where old oslo.messaging notification pool queues remainedin the broker without any consumer after agent restart. The notificationqueues will now be created withamqp_auto_delete=true. Seebug:2004933.

• Fixes an issue causing heavy RAM (and/or-storage) usage on the messagebroker back-end. Theironic-neutron-agent uses oslo.messagingnotifications, with all notification listeners using pools. Since alllisteneres are using pools the default notification queue in messaging isnot consumed (only the pool queues are consumed). The default notificationqueue was continously growing, consuming more and more resources on themessaging back-end. Seeoslo.messaging bug: 1814544 andbug:2004938 for moredetails.