Closed queglay closed 10 months ago
Voting for Prioritization
Volunteering to Work on This Issue
Closing this due to some info being innacurate. I will reopen another ticket
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.
Terraform Core Version
1.5.6
AWS Provider Version
5.3.0
Affected Resource(s)
aws_storagegateway_gateway
Expected Behavior
This resource should be force to actually exist before outputting an ID
Actual Behavior
It's possible for it to occaisionally output an id, and troublingly release downstream dependencies like NFS file shares without the resource actually existing.
Relevant Error/Panic Output Snippet
Its not showing as an error, but a false positive since it attempts to refresh state, but doesn't detect the resource doesn't exist if I check the AWS management console. This fail state isn't always reproducible. If I destroy and recreate everything, the issue can go away but this isn't manageable for production.
Additionally, if I try and destroy it hangs on downstream resources that dont exist. eg:
Terraform Configuration Files
example module to reproduce the issue
Steps to Reproduce
Since the gateway exists in a private subnet, terraform must be run from an instance in the same VPC to reproduce and all instances need internet access.
Debug Output
No response
Panic Output
No response
Important Factoids
This file gateway is being launched in a private subnet
References
No response
Would you like to implement a fix?
None