Comment 4 for bug 1586731
Revision history for this message
| Felix Huettner (felix.huettner) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This bug actually still exists and is not expected behaviour.
A restart of all other openstack services does not lead to stray fanout queues being left in rabbitmq.
I could trace this behaviour to a failure to close the rabbitmq connections of the RemoteResourceC
Please find a minimal patch for this below.
This gets rid of the fanout queues for Port, subnet, network, securitygroup, securitygrouprule and addressgroup. However there are still the ones for SubPort and Trunk left since i did not find out where i can close the connections there.