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

Launch Configurations no longer properly wait for IAM Instance Profile propagation in v0.6.14 #5862

Closed
phinze opened this issue Mar 25, 2016 · 6 comments · Fixed by #5863
Closed

Comments

@phinze
Copy link
Contributor

phinze commented Mar 25, 2016

We fixed #2349 a while ago, but a recent AWS SDK update broke our error detection.

if awsErr.Message() == "Invalid IamInstanceProfile" {

I have a failing test locally - will follow up when I have a fix!

@phinze
Copy link
Contributor Author

phinze commented Mar 25, 2016

For folks running into this in current version - you can work around it by adding a local-exec provisioner with a sleep to your instance profile resource so it waits for propagation before continuing. 👍

phinze added a commit that referenced this issue Mar 25, 2016
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
dharrisio pushed a commit to dharrisio/terraform that referenced this issue Mar 29, 2016
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
@gugahoi
Copy link

gugahoi commented Aug 23, 2016

This seems to still be a problem in Terraform v0.7.1. Any ideas of a fix other than adding sleep?

@jakejscott
Copy link

I'm seeing this issue with Terraform v0.7.1 too

@k2t0f12d
Copy link

Might be a red herring because AWS has had an IAM outage today.

@pghalliday
Copy link

I just ran into this issue I think. I destroyed the deployment and ran apply again and it succeeded the second time around

@ghost
Copy link

ghost commented Apr 20, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants