search

grem11n / terraform-aws-vpc-peering

Terraform module to setup VPC peering connection
https://registry.terraform.io/modules/grem11n/vpc-peering/aws/latest
Apache License 2.0
126 stars 91 forks source link

Remote VPC not found #56

Closed maurosanchezg closed 3 years ago

maurosanchezg commented 3 years ago

Hi, When I run terraform plan in order to plan what I am about to deploy, I'm getting the following error:

$ terraform plan Refreshing Terraform state in-memory prior to plan... The refreshed state will be used to calculate this plan, but will not be persisted to local or remote state storage.

module.aws_vpc_peering.module.single_account_multi_region.data.aws_caller_identity.peer: Refreshing state... module.aws_vpc_peering.module.single_account_multi_region.data.aws_route_tables.peer_vpc_rts: Refreshing state... module.aws_vpc_peering.module.single_account_multi_region.data.aws_region.peer: Refreshing state... module.aws_vpc_peering.module.single_account_multi_region.data.aws_vpc.peer_vpc: Refreshing state... module.aws_vpc_peering.module.single_account_multi_region.data.aws_route_tables.this_vpc_rts: Refreshing state... module.aws_vpc_peering.module.single_account_multi_region.data.aws_vpc.this_vpc: Refreshing state... module.aws_vpc_peering.module.single_account_multi_region.data.aws_region.this: Refreshing state... module.aws_vpc_peering.module.single_account_multi_region.data.aws_caller_identity.this: Refreshing state...

Error: InvalidVpcID.NotFound: The vpc ID 'vpc-xxxxxxx' does not exist status code: 400, request id: 7a276ad6-afb5-42ce-9f1f-e87efd2ee7bf

Error: no matching route tables found for vpc with id vpc-xxxxxxxx

I think there's an issue trying to discover the acepter cross-region VPC which is in ohio in my case (requester is in Virginia)

grem11n commented 3 years ago

Thank you for letting me know, I'll double check.

Could you share your Terraform configuration, please? It would be easier to me to re-produce this issue. Feel free to obfuscate any parts you find necessary

grem11n commented 3 years ago

This issue happened to me occasionally with Terraform 0.14.6 and AWS Provider 3.28.0 However, it looks like this is a temporary issue.

@maurosanchezg, is there a persistent way to reproduce this error?

maurosanchezg commented 3 years ago

Sorry I just got back to this, I ended up using CloudFormation for this so I can't answer you now

grem11n commented 3 years ago

I see. Thank you for the update!

For whoever finds this issue: I have noticed that this issue happens more frequently with Terraform 0.14.6 than 0.13.6. AWS provider version is the same - 3.28.0.

However, it seems to be a rare issue. So, closing this issue for now