[ovn-octavia-provider] loadbalancer stuck in PENDING_X if delete_vip_port fails
Bug #1965732 reported by
Luis Tomas Bolivar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Luis Tomas Bolivar |
Bug Description
Load balancer are stuck in pending_x status if delete_vip_port function fails
with an error different than PortNotFound when::
- deleting a loadbalancer
- failed to created a loadbalancer
The problem comes from proper status update not being sent back to octavia
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
assignee: | nobody → Luis Tomas Bolivar (ltomasbo) |
To post a comment you must log in.
Hi Tomas,
Thanks for the report. I only found a delete_vip_port function in ovn-octavia- provider, so I tagged the ticket accordingly. Please correct me if I'm misunderstanding something.
Is there way a to reproduce this problem? If yes, how? What should be the correct behavior - going to an error state? When the error happens do we miss freeing any other resources other than the db record of the load balancer?