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

Bug #1526116 reported by Divya ChanneGowda
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Undecided
Unassigned
neutron-lbaas (Ubuntu)
Invalid
Undecided
Divya ChanneGowda

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.

Changed in neutron-lbaas (Ubuntu):
assignee: nobody → Divya ChanneGowda (divya-hc)
Revision history for this message
Corey Bryant (corey.bryant) wrote :

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?

Revision history for this message
James Page (james-page) wrote :

Marking distro task as invalid as bug task has been raised upstream.

Thanks!

Changed in neutron-lbaas (Ubuntu):
status: New → Invalid
Revision history for this message
Bernard Cafarelli (bcafarel) wrote :

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.