-
Notifications
You must be signed in to change notification settings - Fork 18
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
Build failures related to AWS instantiation #67
Comments
Running with 0.8.2 fwiw. This looks like hashicorp/terraform#6813, except this time it looks like the subnet hasn’t been created by the time the instance is ready to use it. It’s worth seeing whether adding explicit dependencies or seeing whether it happens when we use a remote region per hashicorp/terraform#7527 |
Failure in build 279
While there was an error during |
Failure in build 296
|
- Travis CI runs in us-east-1. Increase latency to help with eventual consistency problem in terraform by running our tests in us-west-2
* Rotate AWS ssh keys * Use Debian 8.7 AMIs * Update regions (Add Sydney and Oregon. Remove Singapore) * Run CI in us-west-2 to try to help with #67 (Travis CI runs in us-east-1. Increase latency to help with possible eventual consistency problem in terraform by running our tests in us-west-2)
Hasn’t reoccured in ages (possibly since #73), without any other upgrades of tf. Closing. |
Build 254 failed due to problems on the AWS side. It timed out waiting for ssh access with the following error:
The terraform destroy then failed with:
The immediate followup terraform apply then failed with:
Then the final terraform destroy failed with the same sort of dependency violation:
The first problem is new since I fixed terraform apply. The failure also happened in build #278 but I re-ran it before capturing the output.
The text was updated successfully, but these errors were encountered: