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
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.
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) |
To post a comment you must log in.
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?