Description of problem:
When we attempt to live migrate instances, we get this error:
ERROR oslo_messaging.notify.messaging NotFound: Queue.declare: (404) NOT_FOUND - failed to perform operation on queue 'versioned_notifications.info' in vhost '/' due to timeout
Version-Release number of selected component (if applicable):
All the time
Steps to Reproduce:
1. deploy OSP12
2. live migrate instances between 2 hosts
Migration is not working with nova complaining that it's unable to find the Q.
I've found this BZ  that lead me to .
When we change the notification_format from "both" (default) to "unversioned" we don't have the error anymore and migration works.
This seems to be a known issue: 1478274
Fixed upstream in https://review.openstack.org/522644
This bugzilla has been removed from the release since it has not been triaged, and needs to be reviewed for targeting another release.
Marking the bug as VERIFIED. Verification steps:
1. create instances. Start/stop them. Live migrate them across a few compute nodes.
2. List the notification queues inside the rabbitmq container and validate that versioned_notifications are gone:
[heat-admin@controller-0 ~]$ sudo docker exec rabbitmq-bundle-docker-0 rabbitmqctl list_queues | grep notifications
3. Verify `notification_format` in the nova.conf:
[heat-admin@compute-0 ~]$ sudo docker exec -ti -u root nova_compute bash
()[root@compute-0 /]# grep notification_format /etc/nova/nova.conf
[heat-admin@compute-0 ~]$ sudo grep notification_format /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf
[heat-admin@controller-0 ~]$ sudo docker exec -ti nova_api bash
()[root@controller-0 /]# grep notification_format /etc/nova/nova.conf
[heat-admin@controller-0 ~]$ sudo grep notification_format /var/lib/config-data/puppet-generated/nova/etc/nova/nova.conf
Note that the issue still persists on the undercloud where I can still see versioned notifications:
(overcloud) [stack@undercloud-0 ~]$ sudo rabbitmqctl list_queues name consumers messages | grep notifications
versioned_notifications.info 0 51
notifications.info 0 104
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.