-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Terraform fails with empty string errors #1574
Comments
If reading an S3 bucket's state, and that bucket has been deleted, don't fail with a 404 error. Instead, update the state to reflect that the bucket does not exist. Fixes hashicorp#1574.
Found the issue. I guess it could be considered a bug in the AWS SDK that some of its errors |
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. |
Since updating from master a week or two ago, Terraform has started giving me mystery errors:
If I run it with
TF_LOG=1
and grep for errors, I see a lot of this:I'm confused because it says "1 error(s) occurred:" but then there's no error, and the logs say "[ERROR]" and then explain that there's an empty list of errors.
A guess: I recently deleted some resources through the AWS web console, which is necessary because destroy doesn't work (#922). Running refresh should notice this, and remove the resource from the state file, but it's a common bug for providers to forget about that case (#889). I think I might be hitting such a case somewhere, but without any actual error messages I can only guess.
Sorry I can't narrow it down any more -- I realize this is totally unreproducable. But maybe since this seems like a recent change to master, someone remembers some change that might be relevant.
The text was updated successfully, but these errors were encountered: