We are writing an external listener to listen to the notifications. To have minimum intervention to the
notifications.infoqueue which is consumed by OSP internally, we have enabled
versioned_notifications.infoqueue by setting
/var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.confon all compute nodes and restarting all the nova related containers. This works in our other clusters but in this specific cluster we see that the
versioned_notifications.infoqueue is set to durable and we suspectthat is preventing the messages from being written to the queue.
How to set the durable flag to false? It is set to false on our other clusters where
versioned_notifications.infoqueue works as expected and in this environment we see this:
[root@overcloud-controller-1 /]# rabbitmqctl list_queues name consumers messages durable| grep notifications notifications.info 0 93 false notifications.error 0 0 false versioned_notifications.info 0 0 true
- Red Hat OpenStack Platform 13.0 (RHOSP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.