[Bug 1526116] Re: 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

Corey Bryant corey.bryant at canonical.com
Thu Jan 5 21:06:41 UTC 2017


I've added upstream neutron to this bug since I think it is not an
Ubuntu packaging bug.  Divya, are you still working on this?

** Also affects: neutron
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, 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

Status in neutron:
  New
Status in neutron-lbaas package in Ubuntu:
  New

Bug description:
  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.

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



More information about the Ubuntu-openstack-bugs mailing list