bug: Error creating route when using multiple subnets in one vpc #7915
Labels
aws:ec2
Amazon Elastic Compute Cloud
status: resolved/fixed
Resolved via a fix or an implementation
type: bug
Bug report
Is there an existing issue for this?
Current Behavior
First of all I'm not a neither an AWS nor a terraform expert. So maybe I'm the problem and not localstack. ;)
I've created to vpc "foo" and "bar" where both vpcs have two subnets (a private and a public one). I want to setup vpc peering between those two vpcs. I'm able to create the peering connection. After that I would like to add the corresponding routes to the route tables where the subnets are associated to.
During the creation of the routes localstack complains about the fact, that the desired destination cidrs already exist. If I query the existing route tables I can see that this is not the case.
Expected Behavior
Routes should be created.
How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
My terraform script:
Error messages:
Output of "awslocal ec2 describe-route-tables --filter Name=route-table-id,Values=rtb-8f86de50"
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: