Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on destroy: Resource cannot be deleted because it is not empty #7

Open
nthomson-pivotal opened this issue Mar 29, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@nthomson-pivotal
Copy link
Collaborator

This error tends to happen on GCP modules:

Error: Error reading ManagedZone: googleapi: Error 400: The resource named 'somezonename' cannot be deleted because it is not empty, containerNotEmpty

This is because external DNS doesn't seem to have time to clean up its records before its terminated, and GCP does not support forceful DNS zone deletion.

Open the DNS zone in the Google Cloud console, manually delete the records and re-run destroy.

@nthomson-pivotal nthomson-pivotal added the bug Something isn't working label Mar 29, 2020
@nthomson-pivotal
Copy link
Collaborator Author

Should be fixed, leaving open for tracking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant