Error Codes

Status Code

Error Code

Error Message

Error Description

Solution

400

EVS.0001

invalid tenant id!

Incorrect tenant ID in the URI.

The tenant ID is the same as the project ID.

Use the correct tenant ID.

400

EVS.0002

invalid token!

Header parameters in the HTTP request are incorrect.

Use the correct token.

403

EVS.0003

invalid token roles!

The token used is incorrect.

The account permission set is empty. Add the required permissions to this account.

400

EVS.1001

null volume!

The name and description formats set in the request to update the disk are incorrect.

Enter the disk name and description in the correct format.

400

EVS.1002

invalid volume id!

Incorrect disk ID.

Enter the disk ID in the correct format.

400

EVS.1003

invalid volume name!

Incorrect disk name format.

Enter the disk name in the correct format.

400

EVS.1004

invalid volume description!

Incorrect disk description format.

Enter the disk description in the correct format.

400

EVS.1005

size of metadata is too large!

The size of the metadata set in the request to create the disk exceeds the upper limit.

Check whether the metadata is too large. The metadata size must be smaller than 1048576 bytes.

400

EVS.1006

invalid backup id!

The ID of the backup used to create the disk is incorrect.

Enter the correct backup ID.

400

EVS.1007

volume name and description can not both be empty!

Parameters name and description are incorrect.

Enter the correct disk name and description.

400

EVS.1008

null createVolumeReq!

The format of the request to create the disk is incorrect.

Use the correct request format.

400

EVS.1009

invalid volumeForCreate!

The body of the request to create the disk is incorrect.

Check the body of the request used to create the disk.

400

EVS.1010

invalid volume size!

Parameter size set in the request to create the disk is invalid.

Enter a valid size value.

400

EVS.1011

null extendVolumeReq!

The format of the request to expand the disk capacity is incorrect.

Use the correct request format.

400

EVS.1012

temporary volume!

You do not have the permission to access this disk.

Do not perform operations for a temporary disk as it does not allow any operation.

400

EVS.1013

request transforming failed!

Request conversion error.

Check whether the request body is correct.

400

EVS.1014

volume can not be extended!

Failed to meet the capacity expansion requirements.

Ensure that the disk meets the expansion requirements.

400

EVS.1015

new volume Size must be greater than old Size!

The new size of the disk is incorrect.

Ensure that the new disk capacity is larger than the original disk capacity.

400

EVS.1016

Invalid input received: May specify only one of imageRef, snapshot_id, backup_id!

Only one data source among image, snapshot, and backup can be selected when creating a disk from a data source.

Select one data source.

400

EVS.1018

Type conversion error , parameter type is unexpected

Type conversion error. The parameter type is unexpected.

Check whether the input parameters are correct. See the parameter description in the Elastic Volume Service API Reference.

400

EVS.1020

invalid volume type!

The disk type set in the request to create the disk is incorrect.

Enter a valid disk type.

400

EVS.1021

the quantity of volume is invalid!

The disk quantity set in the request to batch create disks is incorrect.

Enter a valid disk quantity.

400

EVS.1022

the size param is less than backup size!

Parameter size set in the request to create the disk using a backup is incorrect.

Ensure that the entered disk size is larger than the backup size.

400

EVS.1023

invalid filter limit!

Parameter limit in the URL for querying the disk is incorrect.

Ensure that the limit value ranges from 1 to 1000. The default value is 1000.

400

EVS.1024

invalid filter marker!

Parameter marker in the URL for querying the disk is incorrect.

Ensure that the marker value is in the UUID format.

400

EVS.1025

url encoding failed!

Metadata decoding error.

Check whether parameter metadata is correctly specified.

403

EVS.1027

user role is not allowed for this action!

You do not have the rights to perform the operation.

Check whether the account has relevant permissions, or the account is in arrears, does not pass real-name authentication, or has violations.

400

EVS.1031

invalid resources status!

Input value of parameter resources status is invalid.

Specify a valid value for resources status.

400

EVS.1032

invalid resources ID!

Parameter resources id cannot be left empty.

Specify a valid value for resources id.

400

EVS.1033

query quota failed!

Failed to query the tenant quota.

Check whether the tenant quota is configured.

400

EVS.1034

volume count exceeded volume count quota!

Insufficient disk quantity quota assigned to the tenant.

Increase the disk quantity quota.

400

EVS.1036

invalid availability zone!

Parameter availability_zone set in the request to create the disk is incorrect.

Enter the correct AZ.

400

EVS.1039

invalid sort_key!

Input parameter sort_key is incorrect.

Check whether parameter sort_key is correctly specified.

400

EVS.1040

invalid sort_dir!

Parameter sort_dir in the URL for querying the disk is incorrect.

Ensure that the sort_dir value is desc or asc.

400

EVS.1041

invalid filter availablity-zone!

Parameter availability-zone in the URL for querying the disk is incorrect.

Check whether the AZ specified in the request is valid.

400

EVS.1042

volume gigabytes exceeded volume gigabytes quota!

Insufficient disk capacity quota assigned to the tenant.

Increase the disk capacity quota.

400

EVS.1043

encrypt and cmk and passthrougth in metadata is not support when create volume from snapshot or image!

Parameters __system__encrypted, __system__cmkid, and hw:passthrough are not supported when a disk is created from an image or a snapshot.

Check whether the request body is correct. For details, see the metadata field description for creating disks.

400

EVS.1044

backup status must be available when create a volume from it!

The backup cannot be used to create a disk.

The backup is unavailable.

400

EVS.1045

backupDetail returned by FSP is null!

Failed to query the backup details.

Check whether the backup exists. Contact customer service.

400

EVS.1046

volume status must be available, error, error_extending, error_restoring, error_rollbacking when delete volume!

Failed to delete the disk because the disk status is incorrect.

Contact customer service.

400

EVS.1047

snapshot status must be available or error when delete snapshot!

Failed to delete the snapshot because the snapshot status is incorrect.

Contact customer service.

400

EVS.1048

volume status must be available when extend volume!

Failed to expand the disk capacity because the disk status is incorrect.

Ensure that the disk status meets the expansion requirements.

400

EVS.1049

available-zone is not equal to backup available-zone!

The backup used to create the disk is in the incorrect AZ.

The backup and the disk to be created must in the same AZ.

400

EVS.1051

can not batch create volume from backup!

Batch creating disks from a backup is not available.

Batch creating disks from a backup is not available.

400

EVS.1052

invalid http body!

Request conversion error.

Check whether the request body is correct.

400

EVS.1053

the size of volumes to be deleted is too large!

Too many disks are specified in the request for batch deleting disks.

Reduce the number of disks specified in the batch.

400

EVS.1054

invalid shareable parameter!

Input parameter shareable is invalid.

Check whether parameter shareable is correctly specified.

400

EVS.1057

invalid hw:passthrough in metadata!

Input parameter hw:passthrough under metadata is invalid.

Check whether parameter hw:passthrough is correctly specified.

400

EVS.1058

invalid metadata filter!

Metadata decoding error.

Check whether parameter metadata is correctly specified.

400

EVS.1061

The Volume Tags is Exceed Max Limit Num.

The tag quantity of this EVS disk exceeds the upper limit.

Ensure that the tag quantity of the disk is within the upper limit.

400

EVS.1062

invalid tag!

Invalid tag.

Check the formats of the tag key and tag value and ensure that the formats are correct.

400

EVS.1063

invalid full_clone in metadata!

Input parameter full_clone under metadata is invalid.

Check whether parameter full_clone in metadata is correctly specified.

400

EVS.1064

volume status must be available or in-use when extending!

A disk can be expanded only when its status is available or in-use.

Ensure that the disk is in the available or in-use state before expansion.

400

EVS.1065

multiattach volume status must be available when extending!

A shared disk can be expanded only when its status is available.

Ensure that the shared disk is in the available state before expansion.

400

EVS.1066

status of ECS or BMS does not support volume online extension!

The ECS or BMS status does to meet the requirement of online disk expansion.

Ensure that the ECS or BMS status meets the requirement.

400

EVS.1070

invalid request.

Request conversion error.

Check whether the request body is correct.

500

EVS.2001

submit job failed!

Failed to submit the task.

Contact customer service.

500

EVS.2002

internal error!

The system is currently unavailable.

Contact customer service.

500

EVS.2005

client exception!

A connection exception occurs.

Contact customer service.

500

EVS.2007

update volume timeout!

Updating the metadata of the disk timed out.

Try again later or contact customer service.

500

EVS.2010

exchange token failed!

Failed to obtain the token for the tenant.

Check the user permissions.

500

EVS.2011

delete orderId and productId timeout!

Deleting order information from the disk metadata timed out.

Try again later or contact customer service.

500

EVS.2013

assume role error!

Failed to elevate the permissions.

Contact customer service.

500

EVS.2014

thread is interrupted when sleep!

Failed to escalate rights.

Try again later or contact customer service.

500

EVS.2019

snapshot is error_deleting!

Failed to delete the snapshot because the snapshot is in the error_deleting status.

Contact customer service.

500

EVS.2020

volume is error_deleting!

Failed to delete the disk because the disk is in the error_deleting status.

Contact customer service.

500

EVS.2021

volume is error_detaching!

The disk status is error_detaching.

Try again later or contact customer service.

500

EVS.2023

ConnectException happened!

Network connection timed out.

Try again. If the network fails, check the network status.

If the network status is normal, contact customer service.

500

EVS.2024

volume is error!

The status of the created disk is error.

Contact customer service.

500

EVS.2025

volume is error_restoring!

The status of the created disk is error_restoring.

Contact customer service.

500

EVS.2026

volume is error_extending!

Failed to expand the disk capacity because the disk is in the error_extending state.

Contact customer service.

500

EVS.2029

The size of joIdList and resultList are mismatched!

Incorrect subtask quantity.

Contact customer service.

500

EVS.2030

query context based on parent jobId exception!

Failed to submit the subtask again.

Contact customer service.

500

EVS.2031

result queried from context is null!

Failed to query the context.

Contact customer service.

500

EVS.2032

some volume count quota usage params are null!

Failed to query the disk quantity quota assigned to the tenant.

Try again later or contact customer service.

500

EVS.2033

some volume gigabytes quota usage params are null!

Failed to query the disk capacity quota assigned to the tenant.

Try again later or contact customer service.

500

EVS.2034

domainId decoded from token is null or empty!

Token resolution failure.

Check whether the account information is correct.

500

EVS.2035

domainName decoded from token is null or empty!

Token resolution failure.

Check whether the account information is correct.

500

EVS.2036

the result of decode token is null!

Empty token.

Check whether the account information is correct.

400

EVS.2040

The status of encrypt Key is not enable!

Incorrect key status.

Ensure that the key status is correct.

400

EVS.2041

The encrypt Param is invalid!

The input encryption parameter is invalid.

Check whether the encryption parameter in the request body is correct.

500

EVS.2042

Failed to create cmk.

Failed to create the CMK.

Try again later or contact customer service.

400

EVS.2043

The status of snapshot is not available or backing-up.

The snapshot status is in correct.

Ensure that the snapshot status is available or backing-up.

404

EVS.2044

Failed to check the role of kms.

Failed to check KMS.

Try again later or contact customer service.

400

EVS.2045

invalid snapshot_id!

Input parameter snapshot_id is invalid.

Ensure that the input snapshot_id value is correct.

400

EVS.2046

invalid imageRef!

Input parameter imageRef is invalid.

Ensure that the input imageRef value is correct.

400

EVS.2047

the metadata Param is not allowed to be updated!

The metadata field cannot be modified.

Ensure that the input metadata value is correct.

500

EVS.2050

set volume Qos failed!

Failed to set the disk QoS.

Ensure that the input qos value is correct.

400

EVS.2052

the job result using order id to query is invalid!

The job corresponding to the order ID is not unique.

Try again later or contact customer service.

400

EVS.2053

The az information from request is invalid!

Input parameter availability_zone is invalid.

Ensure that the input availability_zone value is correct.

400

EVS.2054

Cannot create volume from snapshot as the az is invalid!

When the disk is created from a snapshot, the input availability_zone value of the disk is inconsistent with that of the snapshot.

Ensure that the availability_zone value of the disk is consistent with that of the snapshot.

400

EVS.2055

can not create encrypt volume because hasn't xrole.

KMS access rights have not been granted to EVS.

Before you use the disk encryption function, KMS access rights need to be granted to EVS. Grant the KMS access rights to EVS on the management console. After the rights have been granted, EVS can obtain KMS keys to encrypt or decrypt EVS disks.

For details about how to grant the KMS access rights, see EVS Disk Encryption in the Elastic Volume Service User Guide.

403

EVS.2056

action in pdp check deny!

Fine-grained PDP authentication failed.

Check whether the account has relevant permissions, or the account is in arrears, does not pass real-name authentication, or has violations.

400

EVS.2068

operation failed because of volume be locked

Operations cannot be performed on locked resources.

Unlock the resource and then perform the operation.

400

EVS.2070

VolumeTypes are not supported !

Disk type does not exist.

Try again later or contact customer service.

400

EVS.2071

Invalid input received: Availability zone [%s] do not have volume type [%s]

EVS disks of the specified type are used up in the current AZ. No such resources can be used for creation.

Try again later or contact customer service.

400

EVS.2072

Volume type [SSD] in availability zone [AZ1] is sold out !

Ultra-high I/O disks are used up in the current AZ (AZ1). No such resources can be used for creation.

Note

The ultra-high I/O disk type and AZ1 are used as the sample disk type and AZ. The disk type and AZ vary depending on the actual condition.

Select another disk type or contact customer service.

400

EVS.2078

checkQuotaCapacity request body is invalid.

Request conversion error.

Check whether the request body is empty.

400

EVS.2083

AZ and volume type must not be empty or null!

The AZ or disk type parameter in the request is invalid.

Ensure that the input AZ and disk type parameters are correct.

400

EVS.2084

resource size must greater than zero!

The disk size parameter in the request is invalid.

Check whether the disk size specified in the request body is correct.

400

EVS.2085

when operation type is SPEC_CHG, resource id must not be empty or null!

The disk ID is invalid during expansion.

Check whether the disk ID specified in the request body is correct.

400

EVS.2087

retype failed. please make sure that type is supported and the new one is higher than origin

Invalid request parameter.

Ensure that the new type has higher specifications than the old type.

400

EVS.2089

operation failed because the volume is belong to SDRS

The disk is used by the SDRS service.

Free the disk from SDRS or select another disk.

400

EVS.2093

operation failed because the volume is not EVS

The disk is not an EVS disk.

This operation cannot be performed because the disk is not an EVS disk.

400

EVS.2094

system image is not support to create Multiattach/shareable volume !

A shared disk cannot be created from a system disk image.

A shared disk cannot be created from a system disk image.

400

EVS.2096

Target volumeType[%s] is not matched with snapshot[%s] !

When a disk is created from a snapshot, the disk type of the snapshot's source disk is inconsistent with that of the new disk.

Ensure that the disk type of the snapshot's source disk is consistent with that of the new disk.

500

EVS.2105

Volume can not be reverted, because the encrypt volume's __system__cmkid is not exist!

The ID of the CMK used to encrypt the disk does not exist, or has been deleted and cannot be restored.

Contact customer service.

400

EVS.2108

Request body is invalid.

Request conversion error.

Check whether the request body is correct.

400

EVS.2130

Volume is backing-up, forbidden deleting!

Failed to delete the disk because the snapshot is in the backing-up state when a disk backup is being created.

Wait until the backup is created or contact customer service.

400

EVS.2131

Query server info from ecs fail

Failed to query the server details.

Try again later or contact customer service.

400

EVS.2134

call ecs api - attach volume fail.

Failed to attach the disk.

Try again later or contact customer service.

400

EVS.2142

invalid filter limit, can not greater than 1000.

Request parameter limit cannot be greater than 1000.

Ensure that the limit value ranges from 1 to 1000. The default value is 1000.

401

EVS.2143

You need to create an agency for this project for the first time ever

The account does not have the encryption permission.

Create an agency.

403

EVS.2144

Your account is frozen and resources cannot be used.

Insufficient permission because the account is frozen.

Check whether either of the following conditions exists: (If there are no such conditions, contact customer service.)

  • The account does not pass real-name authentication.

  • The account is in arrears.

403

EVS.2145

Your account is suspended and resources cannot be used.

Insufficient permission because the account is suspended.

Check whether any of the following conditions exists: (If there are no such conditions, contact customer service.)

  • The account payment method is not complete.

  • The account does not pass real-name authentication.

  • The account is in arrears.

400

EVS.5400

Malformed request body.

Incorrect request body parameter and format.

Check whether the parameters and format of the request body are correct.

400

EVS.5400

Malformed request url.

Incorrect request URL parameter and format.

Check whether the parameters and format of the request URL are correct.

400

EVS.5400

Request body and URI mismatch.

Request body and URI mismatch.

Check whether the request body and URI belong to the same API.

400

EVS.5400

Invalid imageRef provided.

The image is unavailable.

Select another image.

400

EVS.5400

Must specify a valid status.

The disk status is incorrect.

Specify a disk that is in the correct state.

400

EVS.5400

offset param must be an integer.

The value of parameter offset must be an integer.

Set the value of parameter offset to an integer.

400

EVS.5400

limit param must be an integer.

The value of parameter limit must be set to an integer.

Set the value of parameter limit to an integer.

400

EVS.5400

limit param must be positive.

The value of parameter limit must be a positive number.

Ensure that the limit value is an integer ranging from 1 to 1000. The default value is 1000.

401

EVS.5401

Authentication required.

This operation is unauthorized.

Call the API after authorization.

403

EVS.5403

Policy check failed.

Insufficient permission.

Add the permission and try again.

403

EVS.5403

metadata can not be operated.

No operation permission.

Modifying parameter metadata is forbidden.

404

EVS.5404

Resource(Volume, Snapshot, Backup .etc) cound not be found.

Resources, such as the disk, snapshot, and backup, do not exist.

Check whether the resources are available.

413

EVS.5413

Insufficient volume quota.

Insufficient disk quotas.

Check whether the disk capacity and quantity quotas are sufficient.

500

EVS.5500

Internal server error.

Internal server error.

Try again later or contact customer service.

503

EVS.5503

Service unavailable.

The service is unavailable.

Try again later or contact customer service.

400

Common.0011

query job fail.

Incorrect tenant ID. The tenant ID is the same as the project ID.

Use the correct tenant ID and ensure that the tenant has desired permissions. The tenant ID is the same as the project ID.

400

Common.0011

No jobs found.

jobId is empty.

Enter the correct jobId value.

400

Common.0011

query job fail.

Failed to query JobVO using jobId.

Check whether the jobId value is correct. If the jobId value is correct, check whether the request is delivered to the target EVS service node. If the request has been delivered, contact customer service to locate the fault. If the request has not been delivered, contact customer service to deliver the request to the target EVS service node.

400

Common.0013

Invalid token in the header.

Failed to parse the token because the token expires or the token string is incomplete.

Obtain the token again and ensure that the token string is complete.

400

Common.0018

Invalid token in the header

The project ID in the URI is different from the project ID in the token.

Ensure that the project ID in the URI is the same as that in the token and try again.