-
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
Launch Configurations no longer properly wait for IAM Instance Profile propagation in v0.6.14 #5862
Comments
For folks running into this in current version - you can work around it by adding a |
AWS changed their error message, which was being used for detection of the specific error that indicates we need to wait for IAM propagation. Behavior is covered by a test now. Fixes #5862
AWS changed their error message, which was being used for detection of the specific error that indicates we need to wait for IAM propagation. Behavior is covered by a test now. Fixes hashicorp#5862
This seems to still be a problem in Terraform v0.7.1. Any ideas of a fix other than adding |
I'm seeing this issue with Terraform v0.7.1 too |
Might be a red herring because AWS has had an IAM outage today. |
I just ran into this issue I think. I destroyed the deployment and ran apply again and it succeeded the second time around |
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. |
We fixed #2349 a while ago, but a recent AWS SDK update broke our error detection.
terraform/builtin/providers/aws/resource_aws_launch_configuration.go
Line 435 in 7501f32
I have a failing test locally - will follow up when I have a fix!
The text was updated successfully, but these errors were encountered: