Error Codes
Description
If an error occurs when an API is called, error information is returned. This section describes the error information for VPC APIs (excluding native OpenStack APIs).
Example of Returned Error Information
{ "code": "VPC.0002", "message": "Available zone Name is null." }
Error Code Description
Module |
HTTP Status Code |
Error Code |
Description |
Error Message |
Handling Measure |
---|---|---|---|---|---|
Public |
400 |
VPC.0002 |
The AZ is left blank. |
Available zone Name is null. |
Check whether the availability_zone field in the request body for creating a subnet is left blank. |
404 |
VPC.0003 |
The VPC does not exist. |
VPC does not exist. |
Check whether the VPC ID is correct or whether the VPC exists under the tenant. |
|
400 |
VPC.0004 |
The VPC status is abnormal. |
VPC is not active, please try later. |
Try again later or contact technical support. |
|
401 |
VPC.0009 |
Real-name authentication fails. |
real-name authentication fail. |
Contact technical support. |
|
Public |
400 |
VPC.0007 |
Inconsistent tenant IDs. |
urlTenantId is not equal tokenTenantId |
The tenant ID in the URL is different from that parsed in the token. |
401 |
VPC.0008 |
Invalid token. |
Invalid token in the header. |
Check whether the token in the request header is valid. |
|
403 |
VPC.2701 |
You do not have permission to perform this operation, or your account balance is insufficient. |
Token not allowed to do this action. |
Check whether the account balance is insufficient or whether your account has been frozen. |
|
Creating a VPC |
400 |
VPC.0101 |
VPC parameters are incorrect. |
Param is invalid. |
Check whether the parameter values are valid based on the returned error message and API reference document. |
409 |
VPC.0114 |
The number of VPCs has reached the maximum allowed limit specified by the quota. |
Quota exceeded for resources: ['router']. |
Clear VPC resources that no longer will be used or apply for expanding the VPC resource quota. |
|
400 |
VPC.0115 |
The VPC name already exists. |
The router name has exist. |
Change the VPC name. |
|
Querying a VPC |
400 |
VPC.0101 |
VPC parameters are incorrect. |
getVpc error vpcId is invalid. |
Ensure that the specified VPC ID is correct. |
404/500 |
VPC.0105 |
The interface fails to invoke the background service. |
Neutron Error. |
Check whether the Neutron service is normal or contact technical support. |
|
500 |
VPC.0106 |
An error is returned for the failure to invoke the background service. |
get router is null. |
Check whether the Neutron service is normal or contact technical support. |
|
Querying VPCs |
400 |
VPC.0101 |
Failed to query the VPCs. |
Query vpc list error. |
Check whether the parameter values are valid based on the returned error message. |
500 |
VPC.0105 |
The interface fails to invoke the background service. |
Neutron Error. |
Check whether the Neutron service is normal or contact technical support. |
|
500 |
VPC.0106 |
The response result of calls to the IaaS OpenStack system is null or empty. |
query routers or getList are null. |
Check whether the Neutron service is normal or contact technical support. |
|
Deleting a VPC |
400/404 |
VPC.0101 |
Invalid parameters. |
Delete router error xx is invalid. |
Check whether the parameter values are valid based on the returned error message. |
500 |
VPC.0102 |
The interface fails to obtain the routing resources. |
Delete router fail. |
Contact technical support. |
|
409 |
VPC.0103 |
The VPC cannot be deleted because it is being created. |
Resource status is busy, try it again later. |
Contact technical support. |
|
409 |
VPC.0104 |
The VPC cannot be deleted because it contains subnets. |
Router contains subnets, please delete subnet first. |
Delete the subnet in the VPC. |
|
404/500 |
VPC.0105 |
The interface fails to invoke the background service. |
Neutron Error. |
Check whether the Neutron service is normal or contact technical support. |
|
409 |
VPC.0107 |
Failed to delete the VPC because it has network ACLs associated. |
Delete the firewall first before deleting the router. |
Delete the network ACLs of the tenant first. |
|
409 |
VPC.0108 |
Failed to delete the VPC because it has EIPs associated. |
Router is used not allow deleted. |
Delete the EIPs of the tenant first. |
|
409 |
VPC.0109 |
Failed to delete the VPC because one or more VPNs have been created for it. |
Router is used not allow deleted. |
Delete VPNs of the tenant. |
|
409 |
VPC.0110 |
The VPC cannot be deleted because its status is unstable. |
deleteDefaultNetworkFromRouter router status is invalid. |
Contact technical support. |
|
500 |
VPC.0111 |
An internal VPC exception occurs. |
Database Error. |
Contact technical support. |
|
409 |
VPC.0112 |
The VPC cannot be deleted because it contains security groups. |
Delete the securitygroup first before deleting the router. |
Delete security groups of the tenant. |
|
409 |
VPC.0118 |
The VPC cannot be deleted because it contains load balancers. |
ELB exists under this router, delete ELB firstly. |
Delete load balancers in the VPC. |
|
500 |
VPC.0119 |
An error occurred when the VPC service makes calls to the ELB service. |
ELB Error. |
Check whether the ELB service is normal or contact technical support. |
|
409 |
VPC.0120 |
The VPC cannot be deleted because it contains extension routes. |
exroutes exists under this router, delete exroutes firstly. |
Delete extension routes in the VPC. |
|
Updating a VPC |
400 |
VPC.0101 |
Invalid parameters. |
Update router xx is invalid. |
Check whether the parameter values are valid based on the returned error message. |
404/500 |
VPC.0105 |
The interface fails to invoke the background service. |
Neutron Error. |
Check whether the Neutron service is normal or contact technical support. |
|
500 |
VPC.0113 |
The VPC cannot be updated because the status of the VPC is abnormal. |
Router status is not active. |
Try again later or contact technical support. |
|
400 |
VPC.0115 |
The VPC name already exists. |
The router name has exist. |
Change the VPC name. |
|
400 |
VPC.0117 |
The subnet parameters are invalid. The VPC CIDR block does not contain all its subnet CIDR blocks. |
Cidr can not contain subnetList cidr. |
Change the CIDR block of the VPC. |
|
Creating a subnet |
400 |
VPC.0201 |
Incorrect subnet parameters. |
Subnet name is invalid. |
Check whether the parameter values are valid based on the returned error message and API reference document. |
500 |
VPC.0202 |
An internal error occurs in the subnet. |
Create subnet failed. |
Contact technical support. |
|
400 |
VPC.0203 |
The CIDR block of the subnet is not in the range of the VPC. |
Subnet is not in the range of VPC. |
Change the CIDR block of the subnet. |
|
400 |
VPC.0204 |
The CIDR block of the subnet already exists in the VPC. |
The subnet has already existed in the VPC, or has been in conflict with the VPC subnet. |
Change the CIDR block of the subnet. |
|
400 |
VPC.0212 |
Invalid subnet CIDR block. |
The subnet cidr is not valid. |
Check whether the subnet CIDR block is valid. |
|
Querying a subnet |
400 |
VPC.0201 |
Invalid subnet ID. |
Subnet ID is invalid. |
Check whether the subnet ID is valid. |
404/500 |
VPC.0202 |
Failed to query the subnet. |
Query subnet fail. |
Contact technical support. |
|
Querying subnets |
400 |
VPC.0201 |
Failed to query the subnets. |
Query subnets list error. |
Check whether the parameter values are valid based on the returned error message. |
500 |
VPC.0202 |
Failed to query the subnets. |
List subnets error. |
Contact technical support. |
|
Deleting a subnet |
400 |
VPC.0201 |
Invalid subnet ID. |
Subnet ID is invalid. |
Check whether the parameter values are valid based on the returned error message. |
404/500 |
VPC.0202 |
An internal error occurs in the subnet. |
Neutron Error. |
Contact technical support. |
|
500 |
VPC.0206 |
The subnet cannot be deleted because it is being used by the VPN. |
Subnet has been used by VPN, please remove the subnet from the VPN and try again. |
Delete the subnet that is used by the VPN. |
|
400 |
VPC.0207 |
This operation is not allowed because the subnet does not belong to the VPC. |
Subnet does not belong to the VPC. |
Check whether the subnet is in the VPC. |
|
500 |
VPC.0208 |
The subnet cannot be deleted because it is being used by the private IP address. |
Subnet is used by private IP, can not be deleted. |
Delete the private IP address of the subnet. |
|
500 |
VPC.0209 |
The subnet cannot be deleted because it is being used by an ECS or load balancer. |
Subnet is still used, such as computer, LB. |
Delete the ECS or load balancer in the subnet. |
|
500 |
VPC.0210 |
The subnet cannot be deleted because it is being used by the custom route. |
Subnet has been used by routes, please remove the routes first and try again. |
Delete the custom route. |
|
500 |
VPC.0211 |
The subnet cannot be deleted because it is being used by load balancers. |
subnet is still used by LBaas. |
Delete load balancers in the subnet. |
|
Updating a subnet |
400 |
VPC.0201 |
Incorrect subnet parameters. |
xx is invalid. |
Check whether the parameter values are valid based on the returned error message. |
404/500 |
VPC.0202 |
An internal error occurs in the subnet. |
Neutron Error. |
Contact technical support. |
|
500 |
VPC.0205 |
The subnet cannot be updated because it is being processed. |
Subnet states is invalid, please try again later. |
Try again later or contact technical support. |
|
400 |
VPC.0207 |
This operation is not allowed because the subnet does not belong to the VPC. |
Subnet does not belong to the VPC. |
Check whether the subnet is in the VPC. |
|
Querying quotas |
400 |
VPC.1207 |
The specified resource type does not exist. |
resource type is invalid. |
Use an existing resource type. |
Assigning a private IP address |
500 |
VPC.0701 |
The private IP address already exists. |
The IP has been used. |
Change another private IP address and try again. |
400 |
VPC.0705 |
Invalid private IP address |
IP address is not a valid IP for the specified subnet. |
Check whether the specified IP address in the request body is within the subnet CIDR block. |
|
404 |
VPC.2204 |
The resource does not exist or the permission is insufficient. |
Query resource by id fail. |
Check whether the specified subnet in the request body exists or the current account has the permission to query the subnet. |
|
Querying a Private IP Address |
404 |
VPC.0704 |
The private IP address does not exist. |
Query resource by id fail. |
Check whether the private IP address exists. |
Querying Private IP Addresses |
400 |
VPC.0702 |
Invalid parameters. |
query privateIps error. |
Check whether the parameter values are valid based on the returned error message. |
Releasing a Private IP Address |
404 |
VPC.0704 |
The private IP address does not exist. |
Query resource by id fail. |
Check whether the private IP address exists. |
500 |
VPC.0706 |
An error occurs when the private IP address is being released. |
Delete port fail. |
Try again later or contact technical support. |
|
409 |
VPC.0707 |
The private IP address is in use. |
privateIp is in use. |
Check whether the private IP address is being used by other resource. |
|
Creating a security group |
400 |
VPC.0601 |
The parameters of the security group are incorrect. |
Creating securitygroup name is invalid. |
Check whether the parameter values are valid based on the returned error message and API reference document. |
500 |
VPC.0602 |
An internal error occurs in the security group. |
Add security group fail. |
Check whether the Neutron service is normal or contact technical support. |
|
409 |
VPC.0604 |
Insufficient security group quota. |
Quota exceeded for resources: ['security_group']. |
Delete the security group that is no longer required or apply for increasing the quota. |
|
Querying a security group |
400 |
VPC.0601 |
The parameters of the security group are incorrect. |
Securitygroup id is invalid. |
Check whether the security group ID is valid. |
500 |
VPC.0602 |
An internal error occurs in the security group. |
Query security group fail. |
Check whether the Neutron service is normal or contact technical support. |
|
404 |
VPC.0603 |
The security group does not exist. |
Securitygroup is not exist. |
Check whether the security group ID is correct or whether the security group exists under the tenant. |
|
404/500 |
VPC.0612 |
An internal error occurs in the security group. |
Neutron Error. |
Contact technical support. |
|
Querying security groups |
400 |
VPC.0601 |
The parameters of the security group are incorrect. |
Query security groups error limit is invalid. |
Check whether the parameter values are valid based on the returned error message and API reference document. |
500 |
VPC.0602 |
An internal error occurs in the security group. |
Query security groups fail. |
Check whether the Neutron service is normal or contact technical support. |
|
Creating a security group rule |
409 |
VPC.0602 |
The security group rule already exists. Insufficient security group rule quota. |
1.Security group rule already exists. 2.Quota exceeded for resources: ['security_group_rule']. |
Change the request body for creating a security group rule. Delete the security group rule that is no longer required or apply for increasing the quota. |
Resource tags |
400 |
VPC.1801 |
Incorrect resource ID. |
resource id is invalid. |
Use a correct resource ID. |
400 |
VPC.1801 |
Invalid action value. |
action is invalid. |
Ensure that the value of action is create or delete. |
|
400 |
VPC.1801 |
Invalid key length. The key can contain 1 to 36 characters. |
Tag length is invalid. The key length must be in range [1,36] and value in range [0,43] |
Use a valid key value. |
|
400 |
VPC.1801 |
Invalid value length. The value can contain 0 to 43 characters. |
Tag length is invalid. The key length must be in range [1,36] and value in range [0,43] |
Use a value of valid length. |
|
400 |
VPC.1801 |
Incorrect resource type. |
Resource_type xxx is invalid. |
Ensure that the value of resource_type is vpcs. |
|
400 |
VPC.1801 |
The tag list contains value null. |
Tag can not be null. |
Use valid tags. |
|
400 |
VPC.1801 |
The matches list contains value null. |
The list of matches contains null. |
Use valid matches. |
|
400 |
VPC.1801 |
The tags exist, but their values are null. |
Tag value can not be null. |
Use valid tags. |
|
400 |
VPC.1801 |
The matches exist, and the value is null. |
The value of Matches in resourceInstancesReq is null. |
Use valid matches. |
|
400 |
VPC.1801 |
The tag list contains more than 10 keys. |
number of tags exceeds max num of 10. |
Use valid tags. |
|
400 |
VPC.1801 |
The tag list contains duplicate keys. |
Tag key is repeated. |
Use valid tags. |
|
400 |
VPC.1801 |
There are duplicate tag values in the tag list. |
Value of tags in resourceInstancesReq is duplicate. |
Use valid tags. |
|
400 |
VPC.1801 |
The tag in the tag list has more than 10 tag values. |
number of tags exceeds max num of 10. |
Use valid tags. |
|
400 |
VPC.1801 |
The key in matches is not the resource name. |
The key of matches is invalid. |
Use valid matches. |
|
400 |
VPC.1801 |
Invalid limit or offset value. |
Limit in resourceInstancesReq is invalid. Offset in resourceInstancesReq is invalid. |
Use valid limit and offset values. |
|
400 |
VPC.1801 |
The tags dictionary structure is missing. |
ResourceInstancesReq is null or invalid. |
Use a valid tags dictionary structure. |
|
400 |
VPC.1801 |
The key in tags exceeds the maximum length or is left blank. |
Tag length is invalid. The key length must be in range [1,36] and value in range [0,43] |
Use valid keys in tags. |
|
400 |
VPC.1801 |
A value in tags exceeds the maximum length. |
Tag length is invalid. The key length must be in range [1,36] and value in range [0,43] |
Use valid values in tags. |
|
400 |
VPC.1801 |
The matches dictionary structure is missing. |
ResourceInstancesReq is null or invalid. |
Use a valid matches dictionary structure. |
|
400 |
VPC.1801 |
The matches are an empty list. |
The number of Matches in resourceInstancesReq is 0. |
Use a valid matches list. |
|
400 |
VPC.1801 |
The matches list contains tag values that contain more than 255 Unicode characters. |
The value's length of Matches in resourceInstancesReq is more than 255. |
Use a valid matches list. |
|
500 |
VPC.1801 |
Incorrect request body format. |
InvalidInput |
Use the correct request body format. |
|
404 |
VPC.2204 |
The resource does not exist or the permission is insufficient. |
Query subnet by id fail. |
Use an existing resource or obtain required permission. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot