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

Terraform does not bubble up VPC Peering errors #8933

Closed
kvz opened this issue Sep 20, 2016 · 5 comments
Closed

Terraform does not bubble up VPC Peering errors #8933

kvz opened this issue Sep 20, 2016 · 5 comments

Comments

@kvz
Copy link
Contributor

kvz commented Sep 20, 2016

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.

@antonbabenko
Copy link
Contributor

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.

@kvz
Copy link
Contributor Author

kvz commented Sep 22, 2016

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!

@kwilczynski
Copy link
Contributor

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

@stack72
Copy link
Contributor

stack72 commented Sep 27, 2016

Closed via #9038

@stack72 stack72 closed this as completed Sep 27, 2016
@ghost
Copy link

ghost commented Apr 22, 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.

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

No branches or pull requests

4 participants