Comment 9 for bug 1595269

yes zoltan, identified fix for this issue.

while testing fix for this, identified another issue which is stopping Loadbalancer delete itself.

Issue: Loadbalancer provisioning_status is inconsistent between Octavia and Neutron Database during LB create failure. https://bugs.launchpad.net/octavia/+bug/1606842

when an amphora is unreachable to controller worker because of network connectivity, loadbalancer provisioning_state will goes into ERROR state, same is status available in neutron DB.

where as in Octavia DB provisioning_state is stuck to PENDING_CREATE.

since we check provisioning_state in Octavia DB to be ERROR while delete, delete is unsuccessful.

for this issue, i raised another bug as https://bugs.launchpad.net/octavia/+bug/1606842

waiting for this to be triage.