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.
(openstackclient-venv) [~] openstack loadbalancer delete 64951486-8143-4a17-a88b-9f576688e662
Validation failure: Cannot delete Load Balancer 64951486-8143-4a17-a88b-9f576688e662 - it has children (HTTP 400) (Request-ID: req-5bf53e03-d33d-4995-88fb-8617060afdf4)
(openstackclient-venv) [~] openstack loadbalancer delete 64951486-8143-4a17-a88b-9f576688e662 --cascade
Invalid state PENDING_UPDATE of loadbalancer resource 64951486-8143-4a17-a88b-9f576688e662 (HTTP 409) (Request-ID: req-cd917d82-67cd-4704-b6d2-032939e08d88)
Wallaby OpenStack deployment using OpenStack Kayobe
Relevant package version:
- octavia-lib: 2.3.1 provider: 1.0.2.dev5
- 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 t-venv) [~] openstack loadbalancer delete 64951486- 8143-4a17- a88b-9f576688e6 62 8143-4a17- a88b-9f576688e6 62 - it has children (HTTP 400) (Request-ID: req-5bf53e03- d33d-4995- 88fb-8617060afd f4)
Validation failure: Cannot delete Load Balancer 64951486-
(openstackclien t-venv) [~] openstack loadbalancer delete 64951486- 8143-4a17- a88b-9f576688e6 62 --cascade 8143-4a17- a88b-9f576688e6 62 (HTTP 409) (Request-ID: req-cd917d82- 67cd-4704- b6d2-032939e08d 88)
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:/ /paste. opendev. org/show/ bkKWy2WkjC9fo05 kOFE3/
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.