Help Center/ Cloud Container Engine/ FAQs/ Cluster/ Cluster Deletion/ What Should I Do If I Can't Delete a Cluster Because of the Load Balancer Deletion Failure?
Updated on 2026-05-25 GMT+08:00
View PDF
Share

What Should I Do If I Can't Delete a Cluster Because of the Load Balancer Deletion Failure?

Symptom

The cluster cannot be deleted, and the following error information is displayed:

Expected HTTP response code [200 202 204 404] when accessing [DELETE https://elb.***.com/v2.0/lbaas/listeners/b8c3f74c-acb9-4b24-a7bb-2e87629f382b], but got 409 instead\n{"NeutronError": {"message": "l7policy a1510d77-13be-4b4b-add7-e7fbe47eec0f is using this listener."}}

Possible Cause

In this example, the listener in use in the load balancer is not deleted.

Solution

Go to the ELB console, manually delete the listener of the corresponding ELB, and delete the cluster again.

Parent Topic: Cluster Deletion