-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Packer fails to find new AWS EC2 Instance #2128
Comments
Also mitchellh/goamz#180 |
@renat-sabitov had already tried patching in #180 , but #1764 looks like it will fix this particular problem and is a better solution than my PR. I'll patch our fork and see how we go. Thanks. |
Fixed by #1764 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Often packer fails to find a newly created AWS EC2 instance. Usually the instance is actually created and the API is just being slow to realise it.
Retrying the check to see if the instance has been created would probably fix this.
In our environment, in the previous 28 days packer has failed to find 204 successfully created instances causing us to have to manually mop up the instances, keys and groups.
The text was updated successfully, but these errors were encountered: