Error Codes
If an error occurs in API calling, no result is returned. Identify the cause based on the error code of each API. If an error occurs in API calling, HTTP status code 4xx or 5xx is returned. The response body contains the specific error code and information. If you fail to locate the cause of an error, contact customer service and provide the error code, so that we can help you solve the problem as soon as possible.
Format of an Error Response Body
If an error occurs during API calling, an error code and a message will be displayed. The following shows an error response body.
{ "errorMessage": "The format of message is error", "errorCode": "CCE.01400001" }
In the preceding information, errorCode is an error code, and errorMessage describes the error.
Error Code Description
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in Error Codes.
Status Code |
Error Code |
Error Message |
Description |
Troubleshooting |
---|---|---|---|---|
400 |
CCE.01400001 |
Invalid request. |
Invalid request body. |
Modify the request body based on the returned message and the CCE API documentation, or contact technical support. |
400 |
CCE.01400002 |
Subnet not found in the VPC. |
No subnet is found in the VPC. |
Check whether the subnet in the request body is in the corresponding VPC. |
400 |
CCE.01400003 |
IPv6 not supported for the subnet. |
The subnet does not support IPv6. |
Use a subnet that supports IPv6. |
400 |
CCE.01400004 |
No available flavors for master nodes. |
There is no available flavor for the master node. |
Change to another available cluster flavor or contact technical support. |
400 |
CCE.01400005 |
Container network CIDR blocks conflict. |
The container CIDR block conflicts with the existing one. |
Check the container CIDR block based on the returned message. |
400 |
CCE.01400006 |
Content type not supported. |
The content type is invalid. |
Use the supported content type by referring to the CCE API documentation. |
400 |
CCE.01400007 |
Insufficient cluster quota. |
Insufficient cluster quota. |
Submit a service ticket to increase the cluster quota. |
400 |
CCE.01400008 |
Insufficient server quota |
Insufficient ECS quota. |
Submit a service ticket to increase the ECS quota. |
400 |
CCE.01400009 |
Insufficient CPU quota. |
Insufficient ECS CPU quota. |
Submit a service ticket to increase the ECS CPU quota. |
400 |
CCE.01400010 |
Insufficient memory quota. |
Insufficient ECS memory quota. |
Submit a service ticket to increase the ECS memory quota. |
400 |
CCE.01400011 |
Insufficient security group quota. |
Insufficient security group quota. |
Submit a service ticket to increase the security group quota. |
400 |
CCE.01400012 |
Insufficient EIP quota. |
Insufficient EIP quota. |
Submit a service ticket to increase the EIP quota. |
400 |
CCE.01400013 |
Insufficient volume quota. |
Insufficient disk quota. |
Submit a service ticket to increase the disk quota based on the returned message. |
400 |
CCE.01400014 |
Excessive nodes in the cluster. |
The number of nodes exceeds the cluster scale. |
Submit a service ticket to change the cluster flavor. |
400 |
CCE.01400015 |
Version not supported. |
The cluster version is not supported. |
Create a cluster of the supported version based on the returned message. |
400 |
CCE.01400016 |
Current cluster type does not support this node flavor. |
The current cluster type does not support this node flavor. |
Use the correct node flavor based on the returned message. |
400 |
CCE.01400017 |
No available container CIDR block found. |
No available container CIDR block is found. |
Use a correct container CIDR block based on the returned message. |
400 |
CCE.01400018 |
This type of OS cannot be created in this CCE version. |
The current CCE version does not support this type of OS. |
Use a supported OS based on the returned message. |
400 |
CCE.01400019 |
Insufficient resource tenant quota. |
The quota of the resource tenant is insufficient. |
Rectify the fault based on the returned message or contact technical support. |
400 |
CCE.01400020 |
Insufficient VPC quota. |
Insufficient VPC quota. |
Rectify the fault based on the returned message or contact technical support. |
400 |
CCE.01400021 |
No available flavors for nodes. |
There is no available flavor for the node. |
Change to another available node flavor or contact technical support. |
400 |
CCE.01400022 |
No available node volumes for nodes. |
There is no available EVS disk flavor for the node. |
Change to another available EVS disk flavor or contact technical support. |
400 |
CCE.02400001 |
Invalid request. |
Invalid request body. |
Modify the request body based on the returned message and the CCE API documentation, or contact technical support. |
400 |
CCE.03400001 |
Invalid request. |
Invalid request body. |
Modify the request body based on the returned message and the CCE API documentation, or contact technical support. |
400 |
CCE.03400002 |
Missing access key. |
The access key is missing. |
Ensure that the version of the installed or upgraded storage add-on is correct, or contact technical support. |
401 |
CCE.01401001 |
Authorization failed. |
Authentication failed. |
Rectify the fault based on the returned message or contact technical support. |
401 |
CCE.02401001 |
Authorization failed. |
Authentication failed. |
Rectify the fault based on the returned message or contact technical support. |
401 |
CCE.03401001 |
Authorization failed. |
Authentication failed. |
Rectify the fault based on the returned message or contact technical support. |
403 |
CCE.01403001 |
Forbidden. |
Access denied. |
Rectify the fault based on the returned message or contact technical support. |
403 |
CCE.02403001 |
Forbidden. |
Access denied. |
Rectify the fault based on the returned message or contact technical support. |
403 |
CCE.03403001 |
Forbidden. |
Access denied. |
Rectify the fault based on the returned message or contact technical support. |
404 |
CCE.01404001 |
Resource not found. |
Resources not found. |
Check whether the resource to be accessed has been deleted. |
404 |
CCE.02404001 |
Resource not found. |
Resources not found. |
Check whether the resource to be accessed has been deleted. |
404 |
CCE.03404001 |
Resource not found. |
Resources not found. |
Check whether the resource to be accessed has been deleted. |
409 |
CCE.01409001 |
The resource already exists. |
The resource already exists. |
Delete the resource and try again. |
409 |
CCE.01409002 |
Resource updated with out-of-date version. |
An out-of-date version is used to update the target resource. |
Ensure that the target resource version is the latest one or contact technical support. |
409 |
CCE.02409001 |
The resource already exists. |
The resource already exists. |
Delete the resource and try again. |
409 |
CCE.03409001 |
Addon instance has installed. |
The add-on instance has been installed. |
Delete the add-on instance and install it again. |
429 |
CCE.01429002 |
Resource locked by other requests. |
The resource is locked by another request. |
Rectify the fault based on the returned message or contact technical support. |
429 |
CCE.02429001 |
The throttling threshold has been reached. |
The maximum number of requests has been reached. |
Reduce the frequency of sending requests or contact technical support. |
500 |
CCE.01500001 |
Internal error. |
Internal error. |
Rectify the fault based on the returned message or contact technical support. |
500 |
CCE.02500001 |
Internal error. |
Internal error. |
Rectify the fault based on the returned message or contact technical support. |
500 |
CCE.03500001 |
Internal error. |
Internal error. |
Rectify the fault based on the returned message or contact technical support. |
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