← Back to team overview

yahoo-eng-team team mailing list archive

[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

 

Closing this old launchpad, either it was fixed since last update, or if
still valid please fill a story for neutron-lbaas at
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
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:
  Invalid
Status in neutron-lbaas package in Ubuntu:
  Invalid

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