Closed sudocovik closed 3 months ago
Hi @sudocovik - I'm so sorry you're experiencing this issue.
This seems to be a longstanding issue in the upstream provider/the DO service.
For such cases, where the cloud provider is having quirks, we'd recommend you use a custom timeout to prevent this from happening in the future.
Hi @guineveresaenger - Thanks for reply.
I did increase timeout with
customTimeouts: { delete: '3m', },
but progrma exists immediately without respecting any timeouts.
It makes no sense for me that timeout will do anything. It's not waiting for anything, program receives error and exits.
Describe what happened
I tried to destroy k8s cluster and load balancer which belong to the same VPC. The load balancer got destroyed before destroying VPC unlike the k8s cluster. The program tried to delete VPC before deleting the cluster which resulted in the following error:
* Error deleting VPC: DELETE https://api.digitalocean.com/v2/vpcs/<<uuid>>: 409 (request "<<uuid>>") Can not delete VPC with members
Sample program
Log output
* Error deleting VPC: DELETE https://api.digitalocean.com/v2/vpcs/<<uuid>>: 409 (request "<<uuid>>") Can not delete VPC with members
Affected Resource(s)
VPC & KubernetesCluster
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).