peer_project_id doesn't work with ucloud_vpc_peering_connection.

Question

peer_project_id doesn't work with ucloud_vpc_peering_connection.

hanyouqing opened this issue 4 years ago · 4 comments

There is a argument peer_project_id on the documentation ， but it doesn't works to me, got error below:

Error: error on creating vpc peering connection, api:
[server.RetCodeError] 58002 Get resource info errors

ucloud_vpc_peering_connection works well when I just remove it.

Answer 1 · 2020-09-08T04:11:06.000Z

I checked the log just now and found that the peer_project_id you passed might be wrong which is a number but we want a string like org-xxx.

Answer 2 · 2020-09-08T04:17:03.000Z

In addition, I learned that under the master account, support the inter-project VPC connection in the same region, VPC connection in different regions and inter-project requires the establishment of two UDPN high-speed channels.

Answer 3 · 2020-09-08T08:00:48.000Z

Yeah, you're right I got the wrong peer_project_id for this, I'm going to close this issue. Thanks!

I do have 2 VPCs in different regions but it seems that I don't have to create 2 UDPNs, only 1 UDPN instance works to me in my case.

Answer 4 · 2020-09-08T08:20:40.000Z

VPC connection in different regions and different projects requires the establishment of two UDPN high-speed channels in two projects.
In your scenario, this example should be able to solve.