My cluster deletion is stuck since an hour with the message “Infrastructure ‘scoutflo-test (z39448b70)’ deletion is in progress…”
Even though when I check my AWS console, the cluster no longer exists
Hi @av06 , this operation can take a few hours because we clean up all the resources. Please wait at least 4 hours. Thank you
1 Like
Hi @av06 !
It seems your cluster cannot be deleted due to a dependency violation on a VPC subnet (vpc-0ec975c39c61b9002) still attached to the cluster. You need to unmap it before you can safely proceed to the deletion.
Raw AWS error message
Error: deleting EC2 Subnet (subnet-051a967e3f87d1c2f): DependencyViolation: The subnet 'subnet-051a967e3f87d1c2f' has dependencies and cannot be deleted.\n\tstatus code: 400, request id: 236496c5-0351-4688-a077-3438aa317051\n\n\nError: deleting EC2 Subnet (subnet-08d73d06cc500a2f5): DependencyViolation: The subnet 'subnet-08d73d06cc500a2f5' has dependencies and cannot be deleted.\n\tstatus code: 400, request id: 799e3728-8d99-42e8-8a42-eb90ac1f7be1\n\n\nError: error detaching EC2 Internet Gateway (igw-0ea8beb00799caba7) from VPC (vpc-0ec975c39c61b9002): DependencyViolation: Network vpc-0ec975c39c61b9002 has some mapped public address(es). Please unmap those public address(es) before detaching the gateway.
As mentioned by @rophilogene, cluster deletion might be long (mostly due to object storage buckets deletion being long).
But now from your console, I can see the error described above:
https://new.console.qovery.com/organization/904dc614-1278-4ac8-b7dc-2179632359bd/cluster/39448b70-a8ff-43f9-9750-5ea6d717e484/logs
Cheers
1 Like
@bchastanier @rophilogene thanks for the response. The issue was resolved after deleting my IGW, deleting the Network Interfactes, then deleting the subnet and finally the VPC. The cluster is deleted now 
1 Like