aws_route.peer_route: Error finding route after creating it: error finding matching route for Route table (rtb-9e3329fb) and destination CIDR block (10.184.36.0/22) #267
Labels
bug
Addresses a defect in current functionality.
service/ec2
Issues and PRs that pertain to the ec2 service.
stale
Old or inactive issues managed by automation, if no further action taken these will get closed.
This issue was originally opened by @achalupa74 as hashicorp/terraform#8805. It was migrated here as part of the provider split. The original body of the issue is below.
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
C:\Users\Administrator>terraform -v
Terraform v0.7.2
Your version of Terraform is out of date! The latest version
is 0.7.3. You can update by downloading from www.terraform.io
Affected Resource(s)
Terraform Configuration Files
Debug Output
Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
Panic Output
I, [2016-09-13T01:05:12.225426 hashicorp/terraform#2580] INFO -- : * aws_route.peer_route: Error finding route after creating it: error finding matching route for Route table (rtb-9e3329fb) and destination CIDR block (10.184.36.0/22)
Expected Behavior
Terraform should create the route w/o throwing an error.
Actual Behavior
The route gets created successfully. But the terraform apply completes w/ an error for some reason?
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
This issue is intermittent and doesn't happen every time.
Important Factoids
This is part of a larger TF Apply operation. The route is is created in a different AWS account while setting up a VPC peering connection. The main terraform script creates a peering connection on Account A, then we use a 'local_exec' call to accept the peering connection on account B. then we use the peer_route module (pasted above) to create the required route tables on the account B. For some reason we intermittently see the error shown above and we don't understand why. We have terraform retry count set pretty high (21):
provider "aws" {
region = "${var.region}"
profile = "${var.profile}"
max_retries = 21
alias = "peer_route"
}
The text was updated successfully, but these errors were encountered: