Closed Cedev closed 8 years ago
As a workaround, you can create a service-group on the device with the id for the name
#slb service-group 8a8c6803-c784-496f-9e9e-3c7b07e3f2ae tcp
And then delete the pool in neutron again
$ neutron lb-pool-delete 8a8c6803-c784-496f-9e9e-3c7b07e3f2ae
Deleted pool: 8a8c6803-c784-496f-9e9e-3c7b07e3f2ae
I attempted to create two pools that ended up in the
ERROR
state and were never created on the acos device (the device configuration had the wrong api version).When deleting them (
neutron lb-pool-delete
), the client made requests to delete the service groups from the acos deviceThis error bubbled through the client and was handled by the neutron service
The pools still exist, but are now
PENDING_DELETE
When deleting an object that doesn't exist the error should be suppressed and the call to delete the object should be successful.