Comment 1 for bug 1738100

If I enable admin plugins in rabbitmq and explore what happens, I see only samples in the cloud where the problem exists, not notifications which seems to indicate that the theory with nova services not emitting them (or not being able to submit) is correct.

# rabbitmq-plugins enable rabbitmq_management

# # good cloud
# python `updatedb && locate rabbitmqadmin` -V openstack list queues name message_stats.publish message_stats.deliver -u $u -p $p | grep notifications
| notifications.audit | | |
| notifications.critical | | |
| notifications.debug | | |
| notifications.error | 1 | 1 |
| notifications.info | 52 | 52 |
| notifications.sample | 906 | 906 |
| notifications.warn | | |
| notifications_designate.info | 330 | |
| versioned_notifications.error | 1 | |
| versioned_notifications.info | 17

I can also confirm that those stats increase on the "good" cloud after I start and stop an instance (2 times for start and 2 times for power off: .start and .end events respectively).

# # bad cloud
# python `updatedb && locate rabbitmqadmin` -V openstack list queues name message_stats.publish message_stats.deliver -u $u -p $p | grep notifications
| notifications.audit | | |
| notifications.critical | | |
| notifications.debug | | |
| notifications.error | | |
| notifications.info | | |
| notifications.sample | 36 | 36 |
| notifications.warn | | |
| notifications_designate.error | | |
| notifications_designate.info | 389 | |
| versioned_notifications.error | | |
| versioned_notifications.info | 26 | |