Error Codes
If an error occurs in API calling, no result is returned. Identify the error cause based on the error codes 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 are unable to identify 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, the system returns an error code and message to you. The following shows the format of an error response body:
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "namespace name is already exist",
"reason": "Conflict",
"code": 409,
"errorCode": "CCI.02.409101"
}
In the preceding information, code is an HTTP status code, errorCode is an error code, and message describes the error.
Error Code Description
If an error code starting with APIGW is returned after you call a CCI API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
|
Error Code |
Description |
|---|---|
|
CCI.01.400101 |
Request failed. The request body is invalid. |
|
CCI.01.400102 |
Failed to query namespace details. The namespace to be queried is not specified. |
|
CCI.01.400103 |
Failed to create the network. The request header does not contain the X-User-Token. |
|
CCI.01.400104 |
The maximum of IAM agencies has reached. Submit a service ticket to increase your quota. |
|
CCI.01.400105 |
The namespace name must be specified using fieldSelector, for example, fieldSelector=metadata.name=namespaceName. |
|
CCI.01.400106 |
The request body for importing the volume is invalid. |
|
CCI.01.400107 |
Invalid enterprise project ID. |
|
CCI.01.400201 |
Invalid subnet CIDR block. The subnet CIDR block cannot overlap with other subnets in the VPC. |
|
CCI.01.400202 |
Failed to create the network. The Annotation field of the request body does not contain project_id. |
|
CCI.01.400301 |
Invalid storage class. Supported storage classes are NFS, OBS, and BS. |
|
CCI.01.400302 |
Invalid storage volume ID format. The ID can contain only letters, digits, and underscores (_) and must start and end with a digit or a letter. |
|
CCI.01.400303 |
Invalid length of the storage volume ID. The ID can contain a maximum of 64 characters. |
|
CCI.01.400304 |
Failed to release the storage volume. The delete_volume field is invalid. |
|
CCI.01.400305 |
Failed to import the storage volume. The storage volume status is abnormal. |
|
CCI.01.400306 |
Failed to import the storage volume. The storage volume does not exist. |
|
CCI.01.400307 |
Failed to import the storage volume. The specified NFS storage is not supported. Only storage class nfs-rw is supported. |
|
CCI.01.400308 |
Failed to import the storage volume. The storage specifications are not supported. Supported specifications are SAS, SSD, and SATA. |
|
CCI.01.400309 |
Failed to import the storage volume. The current volume has been imported. |
|
CCI.01.400401 |
Invalid billing request body. The billing status is not supported. |
|
CCI.01.400402 |
Invalid billing request body. The billing resource type is not supported. |
|
CCI.01.400403 |
Invalid billing request body. The operations on internal users are not supported. |
|
CCI.01.400404 |
Invalid billing request body. The resourceinfos does not match scene. |
|
CCI.01.500101 |
Failed to query the cluster address by namespace. |
|
CCI.01.403101 |
Request failed. You have not applied for the GPU OBT. |
|
CCI.01.403102 |
Request failed. You have not applied for the OBS OBT. |
|
CCI.01.403103 |
Authentication failed. The domain in the token does not match the requested domain. |
|
CCI.01.403104 |
Authentication failed. You do not have permission to perform this operation. |
|
CCI.01.403105 |
Failed to create the namespace. You do not have the cci:namespace:create permission. |
|
CCI.01.403106 |
Failed to delete the namespace. You do not have the cci:namespace:delete permission. |
|
CCI.01.403107 |
Failed to update the namespace. You do not have the cci:namespace:update permission. |
|
CCI.01.403108 |
Failed to obtain the namespace details. You do not have the cci:namespace:get permission. |
|
CCI.01.403109 |
Failed to obtain the namespace list. You do not have the cci:namespace:list permission. |
|
CCI.01.403110 |
Failed to create the resource. You do not have the cci:namespaceSubResource:create permission. |
|
CCI.01.403111 |
Failed to delete the resource. You do not have the cci:namespaceSubResource:delete permission. |
|
CCI.01.403112 |
Failed to update the resource. You do not have the cci:namespaceSubResource:update permission. |
|
CCI.01.403113 |
Failed to obtain the resource details. You do not have the cci:namespaceSubResource:get permission. |
|
CCI.01.403114 |
Failed to obtain the resource list. You do not have the cci:namespaceSubResource:list permission. |
|
CCI.01.404101 |
Request failed. The queried agency does not exist. |
|
CCI.01.401102 |
Request failed. You have not authorized the CCI service. |
|
CCI.04.403112 |
Failed to update the chart. The chart version and name must be the same as those in the original chart. |
|
CCI.04.403124 |
Failed to download the chart. Official charts cannot be downloaded. |
|
CCI.04.403125 |
Failed to delete the chart. The chart is in use. |
|
CCI.04.403126 |
The selected chart version has expired. Select a later version. |
|
CCI.04.403129 |
Operation failed. The chart associated with the readme.md file is not an add-on chart. |
|
CCI.04.403130 |
Request failed. You cannot operate the charts of other users. |
|
CCI.04.403131 |
Update failed. Only releases in the Installed or Failed status can be updated. |
|
CCI.04.400104 |
Request failed because the chart version is invalid. The version can contain a maximum of 64 characters and must comply with the SemVer specification, for example, 1.0.0, 1.0.0-alpha, and 1.0.0-alpha+001. |
|
CCI.04.400105 |
The chart ID cannot be left blank. |
|
CCI.04.400111 |
Request failed. This request supports only add-on charts. |
|
CCI.04.400112 |
Request failed. The chart ID cannot contain more than 64 characters. |
|
CCI.04.400113 |
Request failed. The chart ID format is invalid. |
|
CCI.04.400118 |
Request failed. The chart format is incorrect. The file name extension must be .tgz and the size cannot exceed 2 MB. |
|
CCI.04.400119 |
Request failed. The chart is empty. |
|
CCI.04.400121 |
The chart package format is invalid. The chart package name and version must be the same as those described in the chart. |
|
CCI.04.400126 |
Request failed. The add-on version is not specified. |
|
CCI.04.400131 |
Failed to delete the readme file. The language of the request parameters is not supported. Supported languages are Chinese and English. |
|
CCI.04.400201 |
Request failed. The release name cannot be left blank. |
|
CCI.04.400202 |
Request failed. The release name cannot contain more than 24 characters. |
|
CCI.04.400203 |
Request failed. The release name format is invalid. The release name can contain only letters, digits, and underscores (_) and must start with a letter and end with a letter or digit. |
|
CCI.04.400214 |
Failed to update the release because the requested action is invalid. Supported actions are upgrade and rollback. |
|
CCI.04.400218 |
Request failed. Invalid release version. |
|
CCI.04.400302 |
Request failed. Invalid request body. |
|
CCI.04.400304 |
Request failed. The chart package size exceeds 2 MB. |
|
CCI.04.400306 |
An error occurred when verifying the chart package. Check whether the format of the YAML files in the package is correct. |
|
CCI.04.404204 |
Request failed. The release to be queried does not exist. |
|
CCI.04.409112 |
Failed to upload the chart. The chart name already exists. |
|
CCI.04.409123 |
Failed to upload the chart. The chart name conflicts with an official chart name. |
|
CCI.04.409213 |
Failed to create the release. The release name already exists. |
|
CCI.02.400101 |
Failed to create the namespace. The request body is incorrect. |
|
CCI.02.400102 |
Failed to obtain the tenant name. The tenant is not in the whitelist. |
|
CCI.02.400103 |
The request contains an incorrect text type. |
|
CCI.02.400104 |
Failed to create the quota. The request body is incorrect. |
|
CCI.02.400105 |
Failed to update the quota. |
|
CCI.02.400106 |
Failed to create the namespace. The namespace quota is insufficient. |
|
CCI.02.400107 |
Failed to delete the namespace. The namespace is empty and cannot be deleted. |
|
CCI.02.400108 |
Failed to query flavor information by name. The Name field is empty. |
|
CCI.02.400109 |
Failed to create the namespace. The Name field is invalid. |
|
CCI.02.400110 |
Failed to create the namespace. The Flavor field is invalid. |
|
CCI.02.400111 |
Failed to create the namespace. The Flavor field is empty. |
|
CCI.02.400112 |
Failed to create the namespace. The Domain ID field is empty. |
|
CCI.02.400113 |
Failed to create the namespace. The Project ID field is empty. |
|
CCI.02.400114 |
Failed to query the namespace. The Project ID field is empty. |
|
CCI.02.400116 |
Failed to create the namespace. The cluster resource is insufficient. Try again later. |
|
CCI.02.400117 |
Failed to query the namespace. The pagination parameter is invalid. |
|
CCI.02.400118 |
Failed to create the namespace. The Enterprise Project ID field is empty. |
|
CCI.02.400119 |
Failed to create the namespace. Enterprise projects are not supported. |
|
CCI.02.404101 |
Failed to query flavor information. The requested flavor does not exist. |
|
CCI.02.404102 |
Failed to query resource quota information. The requested resource quota does not exist. |
|
CCI.02.404103 |
Failed to query quota information. The requested quota does not exist. |
|
CCI.02.409101 |
Failed to create the namespace. The namespace already exists. |
Last Article: Status Codes
Next Article: Obtaining a Project ID
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.