Public bug reported: As lb and lb listener db entry is deleted before the driver.listener.delete is completed. When listener_delete and loadbalancer_delete is triggered repeatedly, before update_port triggered by listener_delete is finished, loadbalancer_delete triggers delete_port. And when update_port is resumed, tries to fetch port and fails as port is already deleted.
** Affects: neutron-lbaas (Ubuntu) Importance: Undecided Assignee: Divya ChanneGowda (divya-hc) Status: New ** Changed in: neutron-lbaas (Ubuntu) Assignee: (unassigned) => Divya ChanneGowda (divya-hc) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron-lbaas in Ubuntu. https://bugs.launchpad.net/bugs/1526116 Title: Seeing race condition between update_port and delete_port on lbaas vip port when lbaas_listener delete and loadbalancer_delete is called back to back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron-lbaas/+bug/1526116/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs