yahoo-eng-team team mailing list archive

[Felix Huettner <1586731@xxxxxxxxxxxxxxxxxx>]

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 RemoteResourceCache.
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.


** Attachment added: "partial patch"
   https://bugs.launchpad.net/neutron/+bug/1586731/+attachment/5613242/+files/patch_fanout.txt

** Changed in: neutron
       Status: Expired => New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1586731

Title:
  restart neutron ovs agent will leave the fanout queue behind

Status in neutron:
  New

Bug description:
  to reproduce,
  sudo rabbitmqctl list_queues
  restart neutron-openvswitch-agent
  sudo rabbitmqctl list_queues

  
  q-agent-notifier-dvr-update	0
  q-agent-notifier-dvr-update.ubuntu64	0
  q-agent-notifier-dvr-update_fanout_714f4e99b33a4a41863406fcc26b9162	0
  q-agent-notifier-dvr-update_fanout_a2771eb21e914195b9a6cc3f930b5afb	0
  q-agent-notifier-l2population-update	0
  q-agent-notifier-l2population-update.ubuntu64	0
  q-agent-notifier-l2population-update_fanout_6b2637e57995416ab772259a974315e0	3
  q-agent-notifier-l2population-update_fanout_fe9c07aaa8894f55bfb49717f955aa55	0
  q-agent-notifier-network-update	0
  q-agent-notifier-network-update.ubuntu64	0
  q-agent-notifier-network-update_fanout_1ae903109fe844a39c925e49d5f06498	0
  q-agent-notifier-network-update_fanout_8c15bef355c645e58226a9b98efe3f28	0
  q-agent-notifier-port-delete	0
  q-agent-notifier-port-delete.ubuntu64	0
  q-agent-notifier-port-delete_fanout_cd794c4456cc4bedb7993f5d32f0b1b9	0
  q-agent-notifier-port-delete_fanout_f09ffae3b0fa48c882eddd59baae2169	0
  q-agent-notifier-port-update	0
  q-agent-notifier-port-update.ubuntu64	0
  q-agent-notifier-port-update_fanout_776b9b5b1d0244fc8ddc0a1e309d9ab2	0
  q-agent-notifier-port-update_fanout_f3345013434545fd9b72b7f54a5c9818	0
  q-agent-notifier-security_group-update	0
  q-agent-notifier-security_group-update.ubuntu64	0
  q-agent-notifier-security_group-update_fanout_b5421c8ae5e94c318502ee8fbc62852d	0
  q-agent-notifier-security_group-update_fanout_f4d73a80c9a9444c8a9899cbda3e71ed	0
  q-agent-notifier-tunnel-delete	0
  q-agent-notifier-tunnel-delete.ubuntu64	0
  q-agent-notifier-tunnel-delete_fanout_743b58241f6243c0a776a0dbf58da652	0
  q-agent-notifier-tunnel-delete_fanout_ddb8fad952b348a8bf12bc5c741d0a25	0
  q-agent-notifier-tunnel-update	0
  q-agent-notifier-tunnel-update.ubuntu64	0
  q-agent-notifier-tunnel-update_fanout_1e0b0f7ca63f404ba5f41def9d12f00d	0
  q-agent-notifier-tunnel-update_fanout_e86e9b073ec74766b9e755439827badc	1

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1586731/+subscriptions