[ovn-octavia-provider] Octavia LB stuck in PENDING_UPDATE after creation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
High
|
Fernando Royo |
Bug Description
Wallaby OpenStack deployment using OpenStack Kayobe
Running on Ubuntu Focal
Relevant package version:
- octavia-lib: 2.3.1
- neutron-lib: 2.10.2
- ovn-octavia-
I have encountered a bug where after creating an Octavia load balancer it gets stuck and cannot be deleted.
Attempt in Horizon to delete the load balancer are met with the following
Error: Unable to delete Load Balancer: test_ovn_lb. It also reports Provisioning Status: Pending Update.
When attempting to delete via the openstack client I get this response.
(openstackclien
Validation failure: Cannot delete Load Balancer 64951486-
(openstackclien
Invalid state PENDING_UPDATE of loadbalancer resource 64951486-
In the octavia-api.log the following error message is logged in the moments prior to getting stuck in this state. https:/
The only solution to this problem that I have found that works is to edit the Octavia table to change the current Pending State to ERROR.
use octavia
UPDATE load_balancer SET provisioning_status = 'ERROR' WHERE provisioning_status LIKE "PENDING_UPDATE";
This manual edit of the database then allows for the removal of the load balancer via the API:
openstack loadbalancer delete id-here --cascade
This bug is not blocking however it would nice to prevent this from happening again.
description: | updated |
Changed in neutron: | |
importance: | Undecided → High |
Changed in neutron: | |
assignee: | nobody → Fernando Royo (froyoredhat) |
Changed in neutron: | |
status: | New → Invalid |
Hi Jack,
Could you provide some logs from server (file octavia.log) or give more info about the config of the LB that generates the error? (listener/ pool/members, subnets involved...)
Just to figure out the context, because several improvementes had been done during last months in order to avoid this stuck situations.