-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: Error: reading RAM Resource Share (arn:aws:/ram/:eu-west-2:xxxxxx:resource-share/"xxxxxx): couldn't find resource #33701
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @Viktork25 👋 Thank you for taking the time to raise this! Are you able to provide a sample Terraform configuration that exhibits this behavior, as well as debug logging? There's often helpful context in there for for whoever winds up looking into this. |
Hello, we are experiencing this same issue. The odd thing is, when the resource is attempted to get created, it does indeed accept the resource share invitation but fails to create with the error: When I run an apply on the resource again, terraform thinks the resource is tained and wants to replace it. If I apply the resource, the same error occurs and it never thinks the resource is fully created. I'm on Terraform v1.5.7 and AWS provider version 5.13.0, but I've also tried AWS provider version 5.32.1 and the same thing happens. |
Having the exact same error on version 5.16 and terraform 1.5.7 Its also fixable by using a sleep condition (awful approach) but `resource "time_sleep" "wait_15_seconds" { create_duration = "15s" Then proceed to depend on it on the resource_share_accepter resource This leads to the idea that issue is a race condition when resources are created within a few seconds apart |
It seems for us it isn't a matter of waiting. We have the same error Re-deploying is met with a The only way past this problem is to
We tried introducing the delay as mentioned in the previous comment and also in the example on the A time delay and invitation checking are surely good to have, however there is a chance it may only solve part of the problem. Tested with tf |
This functionality has been released in v5.37.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Terraform Core Version
1.1.0
AWS Provider Version
5.14.0
Affected Resource(s)
Error: reading RAM Resource Share (arn:aws:/ram/:eu-west-xxxxxxx:resource-share/xxxxx): couldn't find resource
Expected Behavior
We are trying to connect our transit gateway with a share transit gateway which has auto acceptance in place.The ram share-resource should be working and not tainted as it turns up and have a full transit gateway attachment shared
Actual Behavior
The ram share-resource fails and says that cannot be finded but ch checking the AWS Console, that share-resource is active and is already accepted.
Relevant Error/Panic Output Snippet
Error: reading RAM Resource Share (arn:aws:/ram/:eu-west-2:xxxxxxxxxxxxxx:resource-share/"xxxxxxxxxxxxxxxxxxxxxxx): couldn't find resource
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: