Terraform: Terraform does not bubble up VPC Peering errors

Created on 20 Sep 2016  ยท  5Comments  ยท  Source: hashicorp/terraform

Hi there,

Running terraform 0.7.3, and when VPC CIDRs overlap when trying to set up a peering connection, it terraform is not bubbling up the error:

Error applying plan:

1 error(s) occurred:

* aws_vpc_peering_connection.us-east-1-eu-west-1: Error waiting for VPC Peering Connection (pcx-cfb33ba6) to become available: unexpected state 'failed', wanted target 'pending-acceptance'. last error: %!s(<nil>)

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Amazon does show me why it failed to some extend:

screen shot 2016-09-20 at 14 59 37

Certainly not a blocking issue for me, but thought I'd share.

bug provideaws

All 5 comments

Correct me if I am wrong, but the resource id is aws_vpc_peering_connection.us-east-1-eu-west-1. Are you trying to peer VPCs in different regions ? If so, it is not allowed by AWS.

Yes it was totally my fault. I just thought the error could be bubbled up as more folks my be doing silly things like me :) But thanks for that pointer, it was spot on!

@kvz hi there! This is a good idea! Will look into it.

Closed via #9038

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.

Was this page helpful?
0 / 5 - 0 ratings