Hi, yeyi,
Please be sure the tenant project’s VPC name follows the convention INSTANCE_REGION-INSTANCE_ID, as seen in Creating a private instance | Cloud Data Fusion Documentation.
Additionally, according to Creating a private instance | Cloud Data Fusion Documentation, if you are not using a shared VPC, the allocated IP range for your instance is automatically allocated by Data Fusion, which means that the range can change between attempts. Is it possible that you left any previous configurations without updating your latest attempt (e.g. Firewall rules, Routes, etc.)?
Though this is strange, I found some past cases where requests made by Terraform created some issues in the tenant project. If you are planning to create the instance from Terraform, please do not, and instead create it from the UI.
To further reduce the possible root causes, could you please recreate your instance using the Cloud Console?
Please note that you may need to remove your allocated IP range for the creation through the console to succeed, so it would be necessary to update the newly allocated range in any network configurations like Firewalls.
The last step in Creating a private instance | Cloud Data Fusion Documentation may be missing. Namely: Creating a Cloud Router custom route advertisement. You may find the steps in Advertise custom IP ranges | Cloud Router. Could you please confirm if you performed this step?
You may follow Advertise custom IP ranges | Cloud Router to create the custom route advertisement in the Cloud Router; or if you prefer, you may try Advertise custom IP ranges | Cloud Router to configure this at BGP Session level.
LinkedIn
Twitter
