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

Build failures related to AWS instantiation #67

Closed
edwinsteele opened this issue Jan 19, 2017 · 4 comments
Closed

Build failures related to AWS instantiation #67

edwinsteele opened this issue Jan 19, 2017 · 4 comments
Assignees
Milestone

Comments

@edwinsteele
Copy link
Collaborator

Build 254 failed due to problems on the AWS side. It timed out waiting for ssh access with the following error:

Error applying plan:
1 error(s) occurred:
* Resource 'aws_subnet.default' does not have attribute 'id' for variable 'aws_subnet.default.id’

The terraform destroy then failed with:

Error applying plan:
1 error(s) occurred:
* aws_vpc.default: DependencyViolation: The vpc 'vpc-37803851' has dependencies and cannot be deleted.
	status code: 400, request id: 65192abf-2a43-42f0-95ac-39d50361033c

The immediate followup terraform apply then failed with:

Error applying plan:
1 error(s) occurred:
* aws_subnet.default: Error creating subnet: InvalidSubnet.Conflict: The CIDR '10.0.1.0/24' conflicts with another subnet
	status code: 400, request id: a8b911bc-3300-4f1d-99c7-2074165a1fef

Then the final terraform destroy failed with the same sort of dependency violation:

Error applying plan:
1 error(s) occurred:
* aws_vpc.default: DependencyViolation: The vpc 'vpc-37803851' has dependencies and cannot be deleted.
	status code: 400, request id: adc58245-20e4-48b1-a1c2-211b6ba1c90c

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.

@edwinsteele edwinsteele added this to the Post MVP milestone Jan 19, 2017
@edwinsteele edwinsteele self-assigned this Jan 19, 2017
@edwinsteele
Copy link
Collaborator Author

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

@edwinsteele
Copy link
Collaborator Author

edwinsteele commented Jan 20, 2017

Failure in build 279

1 error(s) occurred:
* aws_instance.connectbox-server: Error launching source instance: InvalidSubnetID.NotFound: The subnet ID 'subnet-1a710241' does not exist
	status code: 400, request id: 7f9f3f98-cb7b-4c2c-a1e3-8616b986ac38

While there was an error during terraform destroy, the retry logic successfully terraform applyed and we successfully connected to the instance (this is the first time that the retry logic has worked)

@edwinsteele
Copy link
Collaborator Author

Failure in build 296

1 error(s) occurred:
* aws_vpc.default: InvalidVpcID.NotFound: The vpc ID 'vpc-c56de4a3' does not exist
	status code: 400, request id: 9ba3296a-23cf-4b02-8f00-cd0f5107a35a

edwinsteele added a commit that referenced this issue Jan 25, 2017
- 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
edwinsteele added a commit that referenced this issue Jan 25, 2017
* 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)
@edwinsteele
Copy link
Collaborator Author

Hasn’t reoccured in ages (possibly since #73), without any other upgrades of tf. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant