VPN Enterprise route to gateway is only created in default route table, not in custom route table associated to subnet

[Morenovf]

Terraform provider version

Terraform v1.11.0

Affected Resource(s)

• opentelekomcloud_vpc_route_table_v1
• opentelekomcloud_enterprise_vpn_connection_v5

Terraform Configuration Files

Debug Output/Panic Output

No panic or crash. The issue is with automatic route creation.

Steps to Reproduce

1. Create an Enterprise VPN connection.

Expected Behavior

When a VPN connection is created, a route to the VPN gateway (e.g., 0.0.0.0/0) should be automatically added to the custom route table associated with the subnet.

Actual Behavior

The route to the VPN gateway is created only in the default route table, which is not associated to any subnet.
As a result, the custom route table associated with the subnet does not have the necessary route, and traffic does not go through the VPN as expected.

Important Factoids

• All subnets are associated with custom route tables.
• The default route table is not associated with any subnet, so the automatically created route is not used.
• Manual addition of the route to the custom route table is required for correct VPN traffic routing.

References

[anton-sidelnikov]

Hi @Morenovf this is not a Terraform issue,the API behavior cannot be modified from our side. Please create a customer request or demand through customer support instead.

[Morenovf]

Hi. Thank you Anton. We have contacted technical support. We will update this thread as soon as we receive a response. Thank you for your attention and follow-up.

[Morenovf]

We are still waiting for a response from the team. They don't yet have a clear workaround for this issue. We will report here if we receive any further communication.