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

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

Closed
hashibot opened this issue Jun 13, 2017 · 2 comments
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.

Comments

@hashibot
Copy link

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)

  • aws_route

Terraform Configuration Files

variable "stack_name" {}
variable "vpc_cidr" {}
variable "remote_route_table_id" {}
variable "vpc_peering_connection_id" {}
variable "region" {}
variable "profile" {}

provider "aws" {
   region = "${var.region}"
   profile = "${var.profile}"
   max_retries = 21
   alias = "peer_route"
}

resource "aws_route" "peer_route" {
  provider = "aws.peer_route"
  route_table_id = "${var.remote_route_table_id}"
  destination_cidr_block = "${var.vpc_cidr}"
  vpc_peering_connection_id = "${var.vpc_peering_connection_id}"
}

output "peer_route_id" {
   value = "${aws_route.peer_route.id}"
}

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:

  1. 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"
}

@hashibot hashibot added the bug Addresses a defect in current functionality. label Jun 13, 2017
@radeksimko radeksimko added the service/ec2 Issues and PRs that pertain to the ec2 service. label Jan 25, 2018
@github-actions
Copy link

github-actions bot commented Apr 4, 2020

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 4, 2020
@github-actions github-actions bot closed this as completed May 4, 2020
@ghost
Copy link

ghost commented Jun 4, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Jun 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.
Projects
None yet
Development

No branches or pull requests

2 participants