Error Description
VPCs or subnets cannot be deleted.
Common Causes
VPC: A VPC can only be deleted when there is no resource associated other than empty subnets (IPs in the subnet are not used), routing tables, and network ACLs.
Subnet: A subnet can only be deleted when it’s not associated with any resource.
Note:
Resources that can be associated with the subnet include CVM, private network CLB, ENI, HAVIP, SCF, TKE, and TencentDB (for MySQL, Redis, TDSQL, etc.).
According to the rules above, VPCs and subnets cannot be deleted in the following cases:
There are cloud resources that have not been completely deleted. For example, after a database is terminated, it is in isolated status, and the database resources in this status actually are not completely released and continue to use the IP resources of the VPC. Therefore, the VPC or subnet cannot be deleted immediately.
Some resources can not be deleted in the VPC console.
Troubleshooting Procedure
2. Click Delete on the right of the VPC to be deleted, and check the associated resources.
Note:
Note that public network CLB instances don’t use VPC resources.
3. Click the VPC ID to enter the details page, click the corresponding cloud resource to enter its details page, and release it.
If the direction to a resource fails, search for the corresponding product in the Tencent Cloud console, go to the resource's console, search for the resource under the VPC ID, and release it.
A TencentDB instance is put into the Isolated status for a certain period after being terminated, during which the resources are not actually released. You need to click Eliminate Now or wait until the instance is automatically eliminated before you can delete the VPC or subnet.
Note:
The Eliminate Now in TencentDB is an async operation. It may take some time for the returning of operation result. You need to wait till the TencentDB instance is completely released.
For more information, see Terminating Instances (for CVM), Deleting CLB Instances, Deleting an ENI, Deleting a Peering Connection,Deleting a Classiclink, Deleting NAT Gateway, Deleting a VPN Gateway, Deleting Direct Connect Gateway, Delete Flow Logs, Network Probe, Releasing HAVIPs, Terminating Instance (for TencentDB for Redis), and Terminating Instance (for TencentDB for MySQL). If the problem persists, contact us for assistance.