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

Instance cannot be destroyed error prevents the output that allows to see what causes the instance destruction #31332

Closed
ilya-scale opened this issue Jun 28, 2022 · 2 comments
Labels
bug duplicate issue closed because another issue already tracks this problem

Comments

@ilya-scale
Copy link

ilya-scale commented Jun 28, 2022

Terraform Version

1.2.1

Description

Right now when an instance is being destroyed, all we get in the console is Error: Instance cannot be destroyed. Since there can be multiple dependencies that lead to one of the property change that lead to instance being destroyed it is very non-obvious often why this is happening.

So perhaps terraform can be altered to instead of throwing this error at once generate a full plan that will show what causes this and only in the end add this error to the log so that both the plan and the error is visible (and not generate the plan file of course in this case).

@ilya-scale ilya-scale added bug new new issue not yet triaged labels Jun 28, 2022
@jbardin
Copy link
Member

jbardin commented Jun 28, 2022

Duplicate of #16392 and #30271

@jbardin jbardin closed this as completed Jun 28, 2022
@crw crw added duplicate issue closed because another issue already tracks this problem and removed new new issue not yet triaged labels Jun 28, 2022
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate issue closed because another issue already tracks this problem
Projects
None yet
Development

No branches or pull requests

3 participants