Waiting for VPC Peering Connection to become available

I know that you’re working on various VPC issues, so you may be aware of this problem. I wanted to cover my bases and report it in case you’re not.

I’m using release 2.2.4 of moto.

I have two tests (written in Terraform) that I run against a Terraform module that sets up a peered connection. It doesn’t matter which order I run the tests, the second one fails with the error below. I’m struggling to come up with self-contained tests to demonstrate the problem, but if the error message can’t help point you at the problem, I’ll work on the tests some more.

module.vpc_pcx_requester.aws_route_table_association.public[0]: Creation complete after 0s [id=rtbassoc-60df5245]
 
Error: Error waiting for VPC Peering Connection to become available: 
Error waiting for VPC Peering Connection (pcx-e88f13a3) to become available
unexpected state 'deleted', wanted target 'pending-acceptance, active'. last error: %!s(<nil>)

  with module.generated_route_tables.aws_vpc_peering_connection.this,
  on ../../main.tf line 15, in resource "aws_vpc_peering_connection" "this":
  15: resource "aws_vpc_peering_connection" "this" { !
make: *** [pytest//home/kbalk/plus3it/tardigrade-ci/tests/terraform_pytest] Error 1

[bblommers]

Well, one step at the time I suppose. I’ll merge the ‘invalid response’ fix into master for now, and I’ll start looking into the VPC Peering Connection problem either tomorrow or this weekend.

[bblommers]

There are some 400 response codes related to an InvalidRouteTableID.NotFound, but they’re in a good format and I think they’re just reporting that the route no longer exists?

Yeah, I believe those 400 responses are expected - there isn’t really any other way to verify whether a route has been deleted, other than waiting until there’s an error response.

Happy to hear it works now!