Error Codes
Description
This section provides the meanings of error codes returned by AS APIs.
Example of Returned Error Information
{"error":{"code":"AS.0001","message":"System error."}}
Error Code Description
HTTP Status Code |
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|---|
500 |
AS.0049 |
Call IAM failed. |
Failed to call the IAM API. |
Try again later or contact technical support. |
400 |
AS.0002 |
Request body is null. |
The message body is empty. |
Enter a valid message body. |
400 |
AS.5101 |
InvalidAS group ID. |
创建诊断报告的接口,传入的参数scaling_group_id不合法。 |
传入正确的参数 |
400 |
AS.5102 |
Invalid diagnosis report ID. |
删除诊断报告时,传入的参数report_id不合法。 |
传入正确的参数 |
400 |
AS.5103 |
Previous diagnosis has not completed. |
诊断报告是先调创建接口创建,创建后,诊断报告的状态就是诊断中,待后台诊断结束,状态会修改为完成,所以创建诊断报告时,如果前一次创建的诊断报告正在诊断中,再次创建就需要报错。 |
等待之前的诊断报告诊断结束后再创建 |
400 |
AS.5104 |
Diagnosis report not found. |
删除诊断报告时,诊断报告不存在。 |
传入正确的参数 |
400 |
AS.5105 |
A maximum of 5 AS group IDs can be specified. |
查询诊断报告时,传入的参数scaling_group_ids的值不能超过5个,传参示例scaling_group_ids=11111,2222,333,444。 |
将参数scaling_group_ids的值减少到5个以下 |
400 |
AS.5106 |
A maximum of 10 report IDs can be specified. |
查询诊断报告时,传入的参数report_ids的值不能超过10个,传参示例report_ids=11111,2222,333,444。 |
将参数report_ids的值减少到10个以下 |
400 |
AS.5107 |
Maximum diagnoses reached for AS group. |
一个伸缩组只能最多创建50个诊断报告,超过50个会报错。 |
删除无用的诊断报告 |
401 |
AS.0005 |
The token of the header in the request is null. |
The header in the request carries no or an empty token. |
Enter a valid token. |
401 |
AS.0006 |
The token of the header in the request is incorrect. |
The header in the request carries an incorrect, invalid, or expired token. |
Enter a valid token. |
404 |
AS.0007 |
The requested resource [%s] could not be found. |
The requested resources are not found. |
Use the correct URL parameter. |
400 |
AS.0008 |
Incorrect ProjectID. |
The project id value carried in the URL is different from that resolved from the token. |
Check whether the parameter in the URL matches that in the token. |
403 |
AS.0011 |
You do not have the rights to perform the operation. |
You do not have the rights to perform the operation. |
Check whether your user roles include include te_admin, as_adm, and other required roles . |
400 |
AS.0022 |
Request body error |
The request is invalid. |
Check whether the request body is in standard JSON format or whether an unsupported parameter exists. |
400 |
AS.0026 |
Scaling action is not allowed in the cooling duration. |
No scaling action is allowed in the cooldown period. |
Try again later. |
400 |
AS.0031 |
Policy does not allow [%s] to be performed. |
Fine-grained authentication failed because no authentication item is specified. |
Add the required authorization item. |
404 |
AS.0033 |
The api version is illegal, only v1 and v2. |
Invalid API ID. |
Enter a correct API ID. |
400 |
AS.0034 |
Failed to execute the policy because the AS group is in active state. |
Failed to trigger the AS policy because a scaling action in the AS group is in progress. |
An AS policy can be automatically triggered only when there is no in-progress scaling action in the AS group. Try again later. |
400 |
AS.1001 |
The value of parameter Start number is invalid. |
The start number value is invalid. |
Enter a valid start number value. |
400 |
AS.1002 |
The value of parameter Limit is invalid. |
The limit value is invalid. |
Enter a valid limit value. |
400 |
AS.1003 |
The AS configuration ID is null. |
The AS configuration ID is empty. |
Add an AS configuration ID. |
400 |
AS.1004 |
The AS configuration does not exist. |
The AS configuration does not exist. |
Use a correct AS configuration ID. |
400 |
AS.1006 |
The AS configuration is in use. |
The AS configuration is being used by an AS group and cannot be deleted. |
Change this AS configuration for the AS group to another one and delete the AS configuration. |
400 |
AS.1007 |
The AS configuration name is null. |
The AS configuration name is empty. |
Add an AS configuration name. |
400 |
AS.1008 |
The AS configuration name is too long. |
The AS configuration name is too long. |
Use an AS configuration name of proper length. |
400 |
AS.1009 |
The AS group ID is null. |
The AS group ID is not specified. |
Add an AS group ID. |
400 |
AS.1011 |
The instance configuration information is null. |
The instance_config field is not specified. |
Enter a valid instance_config value. |
400 |
AS.1014 |
The image ID in the AS configuration is null. |
The image ID is not specified. |
Add an image ID. |
400 |
AS.1015 |
The image in the AS configuration does not exist. |
The image in the AS configuration does not exist. |
Use a correct image ID. |
400 |
AS.1016 |
The specification ID in the AS configuration cannot be null. |
The flavor ID is not specified. |
Add a flavor ID. |
400 |
AS.1017 |
The specification [%s] in the AS configuration does not exist. |
The flavor of the AS configuration does not exist. |
Use a correct flavor ID. |
400 |
AS.1018 |
The specification [%s] and image is not match. |
The flavor and image do not match. |
Check whether the flavor matches the image. If not, modify the configuration. |
400 |
AS.1019 |
The disk of this type is not applicable to the ECS. |
The flavor and disk do not match. |
Check whether the flavor matches the disk type. If not, change the resources. |
400 |
AS.1021 |
The image in the AS configuration is not activated. |
The image in the AS configuration is not activated. |
Use a correct image ID. |
400 |
AS.1022 |
The image in the AS configuration is not available. |
The image in the AS configuration is unavailable. |
Use a correct image ID. |
400 |
AS.1023 |
Invalid AS configuration name. |
The AS configuration name is invalid. |
Use a valid AS configuration name. |
400 |
AS.1024 |
The number of AS configurations exceeds the upper limit. |
The number of AS configurations exceeds the upper limit. |
Delete idle AS configurations or apply for a higher quota. |
400 |
AS.1025 |
The user login mode in the AS configuration is not unique. |
The user login mode in the AS configuration is not unique. |
Use account-and-password or key-pair login mode only. |
400 |
AS.1026 |
The user login mode in the AS configuration is empty. |
The user login mode in the AS configuration is empty. |
Enter a valid key_name value. |
400 |
AS.1027 |
The scaling config personality is invalid. |
The user AS configuration is invalid. |
Enter a valid personality value. |
400 |
AS.1028 |
The disk in the AS configuration is null. |
The disk in the AS configuration is empty. |
Enter a valid disk value. |
400 |
AS.1029 |
The number of system disks in the AS configuration is invalid. |
The number of system disks in the AS configuration is invalid. |
Ensure that there is only one system disk. |
400 |
AS.1030 |
The size of the system disk in the AS configuration is less than the specification required. |
The size of the system disk in the AS configuration is smaller than the requirement. |
Use a proper system disk size. |
400 |
AS.1031 |
The size of the disk in the AS configuration is not correct. |
The size of the disk in the AS configuration is invalid. |
Use a proper disk size. |
400 |
AS.1032 |
The ECS type [%s] in the AS configuration do not support 24 disks. |
The number of disks in the AS configuration exceeds 24. |
Ensure that the number of disks does not exceed the limit. |
400 |
AS.1033 |
Parameter volumeType in the AS configuration is invalid. |
The volumeType of the disk in the AS configuration is invalid. |
Use a valid volume_type value. |
400 |
AS.1034 |
Parameter diskType in the AS configuration is invalid. |
The diskType in the AS configuration is invalid. |
Use a valid disk_type value. |
400 |
AS.1035 |
Parameter adminPass in the AS configuration is invalid. |
The password in the AS configuration fails to meet the complexity requirements. |
Use passwords that meet complexity requirements. |
400 |
AS.1036 |
32-bit operating system (OS) does not support the specification [%s] with 4G memory. |
The memory of 32-bit OS exceeds 4 GB. |
Change the image or the policy. |
400 |
AS.1038 |
Batch deleting the AS configuration failed. |
Deleting AS configurations in batches fails. |
If this error code is returned, use parameter Message to obtain the configuration ID and the failure cause. |
400 |
AS.1039 |
The number of AS configurations is beyond the maximum limit. |
The number of AS configurations to be deleted in batches exceeds the upper limit. |
Delete a maximum of 50 AS configurations at a time. |
400 |
AS.1040 |
The list of AS config to be deleted is null. |
The AS configuration list is empty. |
Add the IDs of the AS configurations to be deleted in batches. |
400 |
AS.1041 |
The eip info of scaling config is null. |
The eip field in the public_ip field is empty. |
Ensure that the eip field is not empty when specifying the public_ip field. |
400 |
AS.1042 |
The bandwidth size of eip is invalid. |
The bandwidth size is invalid. |
Enter a valid bandwidth. |
400 |
AS.1043 |
The eip type of scaling config is invalid. |
The EIP type is invalid. |
Use a valid EIP type. |
400 |
AS.1044 |
The bandwidth charging mode of eip is invalid. |
The bandwidth billing model of the AS configuration is invalid. |
Use a valid bandwidth billing model. |
400 |
AS.1045 |
The bandwidth type of eip is invalid. |
The bandwidth type is invalid. |
Use a valid bandwidth. |
400 |
AS.1046 |
The bandwidth size of eip is null. |
The bandwidth size is not specified. |
Add the bandwidth value of the AS configuration. |
400 |
AS.1049 |
Parameter userdata in the AS configuration is invalid. |
Parameter userdata in the AS configuration is invalid. |
Use a valid userdata. |
400 |
AS.1050 |
The user login mode in the AS configuration is illegal. |
The user login mode in the AS configuration is invalid. |
Use a valid login mode. |
400 |
AS.1052 |
Parameter metadata in the AS configuration is invalid. |
The metadata in the AS configuration is invalid. |
Use a valid metadata, whose maximum length is 512 bytes and the key value cannot contain spaces, $, or periods(.). |
400 |
AS.1053 |
The data image is not available. |
The data image in the AS configuration is unavailable. |
Use a valid data image. |
400 |
AS.1054 |
The size of the data disk in the AS configuration is less than the data image required. |
The size of the data disk in the AS configuration is smaller than what the data image requires. |
Use a proper data disk. |
400 |
AS.1055 |
The system disk is not support to data image. |
A data disk image cannot be used to create a system disk. |
Refer to the error code description. |
400 |
AS.1056 |
The data image in the AS configuration does not exist. |
The data image in the AS configuration does not exist. |
Use a valid data image ID. |
400 |
AS.1057 |
The DSS of the disk in the AS configuration is not available. |
The selected DSS device is unavailable. |
Use a correct DSS device. |
400 |
AS.1058 |
The type of dss in the AS configuration is incorrect. |
The selected DSS device does not support the disk type. |
Change the DSS device or disk type. |
400 |
AS.1059 |
The capacity of dss in the AS configuration is not enough. |
The storage space on the selected DSS device is insufficient. |
Change the DSS device. |
400 |
AS.1060 |
DSS and EVS are used together in the AS configuration. |
You can use either DSS or EVS disks in an AS configuration. |
Refer to the error code description. |
400 |
AS.1061 |
The DSS does not belong to the same AZ in the AS configuration. |
The selected DSS devices must be in the same AZ. |
Change DSS devices so that they are in the same AZ. |
400 |
AS.1062 |
The number of EVS disks with snapshot IDs in the AS configuration is different from that of EVS disks specified in the full-ECS image. |
The number of disks with snapshot IDs in the AS configuration is different from that of EVS disks specified in the full-ECS image. |
Refer to the error code description. |
400 |
AS.1063 |
The disk data backup in a full-ECS image cannot be used to restore the disk in DSS. |
The disk data backup in a full-ECS image is used to restore the disk in DSS. |
Refer to the error code description. |
400 |
AS.1064 |
The data disk you have selected will be restored using the disk data backup in the full-ECS image. Then, data mirroring will be unavailable. |
Your selected data disk will recover from the disk backup in the full-ECS image, and data mirroring is unavailable now. |
Refer to the error code description. |
400 |
AS.1065 |
ECS resources specified in the AS configuration belong to different AZs. |
The VMs in the AS configuration do not belong to the same AZ. |
Use ECS resources (specifications, images, disk) in the same AZ. |
400 |
AS.1066 |
The AS configuration contains EVS disks with invalid snapshot IDs. |
The AS configuration contains EVS disks with invalid snapshot IDs. |
Use a correct snapshot ID. |
400 |
AS.1067 |
The value of parameter Offset number is invalid. |
Parameter offset is invalid. |
Use a valid offset value. |
400 |
AS.1074 |
The value of parameter Marker is invalid. |
Parameter marker is invalid. |
Use a valid marker value. |
400 |
AS.1075 |
The image ID is invalid. |
Image ID in the AS configuration is invalid. |
Use a correct image ID. |
400 |
AS.1085 |
Invalid multi flavor priority policy. |
The priority policy used in multi-flavor AS configuration is invalid. |
Use a valid multi_flavor_priority_policy value. |
400 |
AS.1086 |
AS configuration is not available for AS group |
The AS configuration is unavailable. |
Replace the AS configuration in the AS group. |
400 |
AS.1087 |
The number of flavors in the AS config exceeds the upper limit. |
The number of flavors in the AS configuration reaches the upper limit. |
Ensure that the number of flavors in the AS configuration does not exceed the upper limit. |
400 |
AS.1088 |
The image in the AS configuration you selected is unavailable for the AZ [%s] in AS group. |
The image in the AS configuration is not available in the AZ of the AS group. |
Change another AS configuration or AZ for the AS group. |
400 |
AS.1090 |
Flavor {0} in the AS configuration is incompatible with the image architecture. |
The selected flavor is incompatible with the image architecture. |
Ensure that the selected flavor is compatible with the image architecture. |
400 |
AS.2002 |
The name of the AS group is null. |
The AS group name is empty. |
Add an AS group name. |
400 |
AS.2003 |
The AS group name is too long. |
The AS group name is too long. |
Use an AS group name of proper length. |
400 |
AS.2004 |
Invalid min or max number of instances in the AS group. |
The maximum or minimum number of instances is invalid. |
Enter correct maximum/minimum number of instances for the AS group. |
400 |
AS.2005 |
The expected number cannot be less than the minimum number of instances or greater than the maximum number of instances. |
The expected number of instances in the AS group is invalid. |
Enter a valid number of expected instances for the AS group. |
400 |
AS.2006 |
Invalid cooldown period of the AS group. |
The cooldown period in the AS group is invalid. |
Enter a valid cooldown period for the AS group. |
400 |
AS.2007 |
The AS group does not exist. |
The AS group does not exist. |
Use a correct AS group ID. |
400 |
AS.2008 |
Invalid execution action of the AS group. |
The scaling action of the AS group is invalid. |
Use a correct scaling action for the AS group. |
400 |
AS.2009 |
The AS group ID is null. |
The AS group ID is not specified. |
Add an AS group ID. |
400 |
AS.2010 |
The expected number of instances in the AS group cannot be smaller than the number of instances for which instance protection has been configured. |
The expected number of instances in the AS group cannot be smaller than the number of instances for which instance protection has been configured. |
Ensure that the number of expected instances is no less than the protected instances, or change the expected number of instances after canceling instance protection. |
400 |
AS.2011 |
Invalid AZ in AS group. |
The AZ in the AS group is invalid. |
Use a valid value. |
400 |
AS.2012 |
The VPC of the AS group does not exist. |
The VPC of the AS group does not exist. |
Use a valid value. |
400 |
AS.2013 |
Parameter networks in the AS group is invalid. |
Parameter networks in the AS group is invalid. |
Use a valid value. |
400 |
AS.2014 |
The security group of the AS group does not exist. |
The security group of the AS group does not exist. |
Use a valid value. |
400 |
AS.2015 |
Parameter listenerId in the AS group is invalid. |
The load balancer listener of the AS group is invalid. |
Use a valid value. |
400 |
AS.2016 |
The listener of the AS group does not belong to the vpc. |
The VPC to which the ELB listener in the AS group belongs is different from the VPC in the AS group. |
Change the VPC ID or ELB listener ID. |
400 |
AS.2017 |
The ID of the VPC in the AS group is null. |
The VPC ID in the AS group is not specified. |
Add a VPC ID. |
400 |
AS.2018 |
No AS configuration is in the AS group. |
No AS is configured in the AS group. |
Enable the AS group after adding an AS configuration to the AS group. |
400 |
AS.2019 |
The value of the parameter that specifies whether to forcibly delete an AS group is invalid. |
The value of the parameter that specifies whether to forcibly delete an AS group is invalid. |
Use a valid value. |
400 |
AS.2020 |
The scaling group status is illegal. |
The AS group status is invalid. |
You are not allowed to perform the operation when the AS group is in the current status. |
400 |
AS.2021 |
The current number of instances in the AS group is not 0. |
Deleting the AS group fails because there are instances in it. |
Before deleting the AS group, deleting its instances. |
400 |
AS.2022 |
The AS group name contains invalid characters. |
The AS group name contains invalid characters. |
Use a correct AS group name. |
400 |
AS.2023 |
The number of AS groups exceeds the upper limit. |
The number of AS groups exceeds the upper limit. |
Delete idle AS groups or apply for a higher quota. |
400 |
AS.2024 |
The number of subnets in the AS group exceeds the upper limit. |
The number of subnets in the AS group exceeds the upper limit. |
Ensure that the number of subnets does not exceed the upper limit. |
400 |
AS.2025 |
The number of security groups in the AS group exceeds the upper limit. |
The number of security groups in the AS group exceeds the upper limit. |
Ensure that the number of security groups does not exceed the upper limit. |
400 |
AS.2027 |
The subnet of the AS group does not belong to the vpc. |
The VPC to which some subnets in the AS group belong is different with the VPC in the AS group. |
Change the VPC ID or subnet. |
400 |
AS.2028 |
The modified expected number of instances is the same as the original number. |
The new expected number of instances is the same as the original number. |
Refer to the error code description. |
400 |
AS.2029 |
Invalid health check method of the AS group. |
The health check method for instances in the AS group is incorrect. |
Use a valid health_periodic_audit_method value. |
400 |
AS.2030 |
You are not allowed to modify the lb, AZ, subnet, and security information when the number of instances in the AS group is not 0, the AS group is scaling, or the AS group is in Inservice status. |
You are not allowed to modify the load balancer, AZ, subnet, or security group information when there are instances in the AS group, the AS group is scaling, or the AS group is in Inservice state. |
Check the number of instances in the AS group and the status of the AS group, or try again later. |
400 |
AS.2031 |
Invalid health check period of the AS group. |
The health check period of the AS group is invalid. |
Use a valid health_periodic_audit_time value. |
400 |
AS.2032 |
Invalid instance removal policy. |
The instance removal policy for the AS group is invalid. |
Use a valid instance_terminate_policy value. |
400 |
AS.2033 |
You are not allowed to perform the operation when the AS group is in current [%s] status. |
You are not allowed to perform the operation when the AS group is in the current status. |
Refer to the error code description. |
400 |
AS.2034 |
Invalid notification method of the AS group. |
The notification method for the AS group is invalid. |
Use a valid notification method. |
400 |
AS.2035 |
The number of instances manually added to the AS group exceeds the maximum number of the instances required in the AS group. |
The number of ECSs in the AS group is greater than the upper limit because some ECSs are manually added. |
Add a proper number of ECSs or increase the maximum number of instances in the AS group. |
400 |
AS.2036 |
The number of instances manually deleted is less than the minimum number of the instances required in the AS group. |
The number of ECSs in the AS group is smaller than the lower limit because some ECSs are manually deleted. |
Delete a proper number of ECSs or decrease the minimum number of instances in the AS group. |
400 |
AS.2037 |
The number of listeners in the AS group exceeds the upper limit. |
The number of ELB listeners in the AS group reaches the upper limit. |
Select a proper number of load balancer listeners. |
400 |
AS.2038 |
The type [%s] of ECS in the AZ you selected has been sold out. |
The ECSs of this type have been sold out in the AZ specified for this AS group. |
Refer to the error code description. Change the AZ of the AS group or change the AS configuration for the AS group. |
400 |
AS.2039 |
Parameter protocolPort of the AS group is invalid. |
Parameter protocolPort of the AS group is invalid. |
Use a valid protocolPort. |
400 |
AS.2040 |
Parameter weight of the AS group is invalid. |
Parameter weight of the AS group is invalid. |
Use a valid weight. |
400 |
AS.2042 |
Parameter pool of lbaas in the AS group is invalid. |
The load balancer pool in the AS group is invalid. |
Use a valid pool. |
400 |
AS.2043 |
There is not avalid volume in the AZ [%s] you selected. |
Storage resources of this type are sold out or do not exist in the AZ specified for this AS group. |
Refer to the error code description. Change the AZ of the AS group or change the AS configuration for the AS group. |
400 |
AS.2044 |
The AZ in the AS group is not available. |
The AZ in the AS group is invalid. |
Refer to the error code description. Change the AZ of the AS group. |
400 |
AS.2045 |
The min or max number of instances in the AS group exceeds the upper limit. |
The minimum or maximum number of instances in the AS group exceeds the limit. |
Enter proper maximum and minimum numbers of instances for the AS group. |
400 |
AS.2046 |
Invalid health check grace period of the AS group. |
The grace period for the instance health check is invalid. |
Use a valid health_periodic_audit_grace_period value. |
400 |
AS.2047 |
The AS group is in active status. |
Failed to modify load balancer parameters because a scaling action is ongoing. |
Wait until the scaling action is complete and modify the load balancer parameters again. |
400 |
AS.2053 |
Invalid multi az priority policy. |
The priority policy used for multiple AZs in the AS group is invalid. |
Change the priority policy used for multiple AZs in the AS group. |
400 |
AS.2054 |
The AS group is in active status. |
Failed to change the AZ because a scaling action is ongoing. |
Wait until the scaling action is complete and change the AZ again. |
400 |
AS.3002 |
Invalid AS policy type. |
The AS policy type is invalid. |
Use a valid scaling_policy_type value. |
400 |
AS.3003 |
The information about the AS policy is null. |
When the AS policy is scheduled or periodic, parameter scheduled_policy is empty. |
Use a valid scheduled_policy value. |
400 |
AS.3004 |
Invalid recurrence type in the AS policy. |
The period type is incorrect. |
Use a valid recurrence_type value. |
400 |
AS.3005 |
The end time of the scaling action triggered periodically is empty. |
The end time is not specified for a periodic AS policy. |
Enter a valid end_time value. |
400 |
AS.3006 |
The format of the end time for the scaling action triggered periodically is incorrect. |
The format of the end time for the periodically triggered scaling action is incorrect. |
Use a correct format for the end time. |
400 |
AS.3007 |
The end time of the scaling action triggered periodically must be later than the current time. |
The end time of the scaling action triggered periodically must be later than the current time. |
Ensure that the end time is later than the current time. |
400 |
AS.3008 |
Parameter lanchTime in the AS policy is null. |
The triggering time is not specified. |
Enter a valid launch_time value. |
400 |
AS.3009 |
The format of parameter lanchTime is incorrect. |
The triggering time format is incorrect. |
Use a correct triggering time format. |
400 |
AS.3010 |
The triggering time of the scheduled policy must be later than the current time. |
The triggering time of the scaling action triggered at a scheduled time must be later than the current time. |
Ensure that the triggering time of the scheduled policy is later than the current time. |
400 |
AS.3011 |
The AS policy type is null. |
The AS policy type is not specified. |
Enter a valid scaling_policy_type value. |
400 |
AS.3012 |
Invalid cooldown period in the AS policy. |
The cooldown period in the AS policy is invalid. |
Enter a valid cool_down_time value. |
400 |
AS.3013 |
The AS policy name is null. |
The AS policy name is not specified. |
Enter a valid scaling_policy_name value. |
400 |
AS.3014 |
The length of the AS policy name is invalid. |
The length of the AS policy name is invalid. |
Enter a valid scaling_policy_name value. |
400 |
AS.3015 |
The action in the AS policy is null. |
The execution action in the AS policy is not specified. |
Enter a valid scaling_policy_action value. |
400 |
AS.3016 |
The operation to perform the action in the AS policy is null. |
The operation to perform the execution action in the AS policy is not specified. |
Enter a valid operation value. |
400 |
AS.3017 |
The operation to perform the action in the AS policy action is invalid. |
The operation to perform the action in the AS policy is invalid. |
Enter a valid operation value. |
400 |
AS.3018 |
The number of instances which action in the AS policy operates on is invalid. |
The number of instances to which the AS policy applies is invalid. |
Enter a valid instance_number value. |
400 |
AS.3019 |
The AS group ID in the AS policy cannot be null. |
The AS group ID in the AS policy is not specified. |
Add an AS group ID. |
400 |
AS.3020 |
The AS policy does not exist. |
The AS policy does not exist. |
Use a correct AS policy ID. |
400 |
AS.3021 |
The AS policy ID cannot be null. |
The AS policy ID is not specified. |
Add an AS policy ID. |
400 |
AS.3022 |
The action of the AS policy request body is invalid. |
The action of the AS policy request body is invalid. |
Use a valid action value. |
400 |
AS.3023 |
The period type of the AS policy is null. |
The period type of the AS policy is empty. |
Use a valid recurrence_type value. |
400 |
AS.3024 |
The value of the period type of the AS policy is null. |
The value of the periodically triggered tasks of the AS policy is empty. |
Add a valid recurrence_value value. |
400 |
AS.3025 |
The value of period type of the AS policy is invalid. |
The period type of the AS policy is invalid. |
Use a valid recurrence_type value. |
400 |
AS.3026 |
The alarm ID in the AS policy is null. |
The alarm ID in the AS policy is empty. |
Add an alarm ID. |
400 |
AS.3027 |
The AS policy must be in the inservice status when the AS policy is performed. |
The AS group must be in service when the AS policy is performed. |
Enable the AS group and try again. |
400 |
AS.3028 |
The format of the start time for the scaling action triggered periodically is incorrect. |
The format of the start time for the periodically triggered scaling action is incorrect. |
Use a correct format for the start time. |
400 |
AS.3029 |
The start time of the scaling action triggered periodically must be earlier than the end time. |
The start time of the periodically triggered scaling action must be earlier than the end time. |
Ensure that the start time of the periodic policy is earlier than the end time. |
400 |
AS.3030 |
The alarm in the AS policy does not exist. |
The alarm rule in the AS policy does not exist. |
Modify the alarm rule used by the AS policy. |
400 |
AS.3031 |
Invalid AS policy name. |
The AS policy name is invalid. |
Enter a valid scaling_policy_name value. |
400 |
AS.3032 |
The number of AS policies exceeds the upper limit. |
The number of AS policies exceeds the upper limit. |
Delete idle AS policies or apply for a higher quota. |
400 |
AS.3033 |
The triggering time of the periodic policy is not included in the effective time of the policy. |
The triggering time of the periodic policy falls outside the effective time range of the policy. |
Ensure that the triggering time of the periodic policy is within the range from the start time to the end time. |
400 |
AS.3034 |
The alarm ID in the AS policy is being used by another AS group. |
The alarm ID in the AS policy is being used by another AS group. |
Refer to the error code description. An alarm ID can be used only by the AS policy in one AS group at a time. |
400 |
AS.3035 |
The percentage of instances which action in the AS policy operates on is invalid. |
The percentage of instances to which the AS policy applies is invalid. |
Use a valid instance_percentage value. |
400 |
AS.3036 |
The action in the AS policy operates is not unique. |
The action in the AS policy operates is not unique. |
Select one from instance_percentage or instance_number. |
400 |
AS.3050 |
The alarm ID in the AS policy is illegal. |
The format of the alarm ID in the AS policy is incorrect. |
Use an alarm ID in correct format. |
400 |
AS.3054 |
The scaling resource type in the AS policy is null. |
The scaling resource type in the AS policy cannot be left blank. |
Use a valid scaling_resource_type value. |
400 |
AS.3056 |
The value of the parameter that specifies whether to delete the alarm in the AS policy is invalid. |
The value of the alarm rule used for deleting the scaling policy is invalid. |
Use a valid delete_alarm value. |
400 |
AS.3057 |
The value of parameter sort_by in the request is invalid. |
The sort_by value in the request is invalid. |
Use a valid sort_by value. |
400 |
AS.3058 |
The value of parameter order in the request is invalid. |
The order value in the request is invalid. |
Use a valid order value. |
400 |
AS.4000 |
The value of parameter start_number in the request for the instance is invalid. |
The start_number value in the instance request is invalid. |
Use a valid start_number value. |
400 |
AS.4001 |
The value of parameter limit in the request for the instance is invalid. |
The limit value in the instance request is invalid. |
Use a valid limit value. |
400 |
AS.4003 |
The value of parameter life_cycle_state in the instance request is invalid. |
The life_cycle_state value in the instance request is invalid. |
Use a valid life_cycle_state value. |
400 |
AS.4004 |
The value of parameter health_status in the request for the instance is invalid. |
The health_status value in the instance request is invalid. |
Use a valid health_status value. |
400 |
AS.4005 |
Parameter scaling_group_id in the request for the instance does not exist. |
The scaling_group_id in the instance request does not exist. |
Use a correct scaling_group_id. |
400 |
AS.4006 |
The instance does not exist. |
The instance does not exist. |
Use a correct instance ID. |
400 |
AS.4007 |
The value of the parameter that specifies whether to delete the instance is invalid. |
The value of the parameter that specifies whether to delete the instance is invalid. |
Use a valid value. |
400 |
AS.4008 |
The start time format of the log about the expected number of the instances is incorrect. |
The start time format of the log about the expected number of the instances is incorrect. |
Use a correct format. |
400 |
AS.4009 |
The end time format of the log about expected number of the instances is incorrect. |
The end time format of the log about expected number of the instances is incorrect. |
Use a correct format. |
400 |
AS.4010 |
Parameter start_number in the request for the log about the expected number of instances is invalid. |
The start_number in the request for the log about the expected number of instances is invalid. |
Use a valid start_number value. |
400 |
AS.4011 |
The value of parameter limit in the request for the log about the expected number of instances is invalid. |
The value of limit in the request for the log about the expected number of instances is invalid. |
Use a valid limit value. |
400 |
AS.4012 |
The value of parameter logId in the request for the log about the expected number of instances is invalid. |
The logId in the request for the log about the expected number of instances is invalid. |
Use a valid logId value. |
400 |
AS.4013 |
The list of instances to be deleted is null. |
The list of instances to be deleted is empty. |
Add instances to be deleted. |
400 |
AS.4014 |
The instances do not belong to the same AS group. |
The instances do not belong to the same AS group. |
Select instances in the same AS group. |
400 |
AS.4015 |
The instance is not in the inservice status. |
The instance is not in inservice state. |
Select an inservice instance. |
400 |
AS.4017 |
The requested instance is null. |
The requested instance is empty. |
Enter a valid instance. |
400 |
AS.4018 |
The action of the body in the request to operate the instance is invalid. |
The value of the request body action of the batch instance operation is invalid. |
Use a valid value. |
400 |
AS.4019 |
The list of instances to be added to the AS group is empty. |
The list of instances to be added to the AS group is empty. |
Enter a valid instance. |
400 |
AS.4020 |
The AZ to which the instance belongs is not within the AZ in the AS group. |
The AZ to which the instance belongs is different from the AZ to which the AS group belongs. |
Select a proper instance for the AZ. |
400 |
AS.4021 |
The VPC to which the instance belongs is different from the VPC in the AS group. |
The VPC to which the instance belongs is different from the VPC in the AS group. |
Select a proper instance for the VPC. |
400 |
AS.4022 |
The number of instances added to the AS group exceeds the upper limit. |
The number of instances added to the AS group exceeds the upper limit. |
Add a proper number of instances. |
400 |
AS.4023 |
The added instance has already existed. |
The added instance already exists. |
Select another valid instance. |
400 |
AS.4024 |
The instance is not in the active status. |
The added instance is not in the active state. |
Select an active instance. |
400 |
AS.4026 |
The number of instances deleted exceeds the upper limit. |
The number of instances deleted exceeds the upper limit. |
Delete a proper number of instances. |
400 |
AS.4027 |
The added instance has already existed in other AS group. |
The instance has already been added to another AS group. |
Select another valid instance. |
400 |
AS.4028 |
The AS instance ID cannot be null. |
The instance ID cannot be left blank. |
Use a correct instance ID. |
400 |
AS.4029 |
Failed to add instances in a batch. |
Failed to batch add instances. |
If this error code is returned, use parameter Message to obtain the instance ID and the failure cause. |
400 |
AS.4030 |
Failed to delete instances in a batch. |
Failed to delete instances in batches. |
If this error code is returned, use parameter Message to obtain the instance ID and the failure cause. |
400 |
AS.4032 |
The list of instances is null. |
The list of instances is empty. |
Refer to the error code description. |
400 |
AS.4033 |
Failed to set instance protection in a batch. |
Failed to set instance protection in a batch. |
If this error code is returned, use parameter Message to obtain the instance ID and the failure cause. |
400 |
AS.4043 |
The number of instances exceeds the upper limit. |
The number of instances for batch operations exceeds the upper limit. |
Ensure that the number of instances for batch operations is no more than 10 at a time. |
400 |
AS.7012 |
The ELB listener is unavailable. |
The ELB listener does not exist. |
Modify the ELB listener information. |
400 |
AS.7019 |
The number of private IP addresses in the subnet is insufficient. |
Private IP addresses in the subnet are insufficient. |
Modify the subnet information and enable the AS group. |
400 |
AS.7022 |
The key pair does not exist. |
The SSH key of the AS configuration does not exist. |
Replace the AS configuration in the AS group. |
400 |
AS.7025 |
The topic urn is not valid. |
The notification subject is invalid. |
Use a valid notification subject. |
400 |
AS.7026 |
The topic scene is not valid. |
The notification scene is invalid. |
Use a valid notification scene. |
400 |
AS.7027 |
The topic of notification is null. |
The notification subject is empty. |
Add a notification subject. |
400 |
AS.7028 |
The number of topics in the AS group exceeds the upper limit. |
The number of notifications in the AS group exceeds the upper limit. |
Add a maximum of five notifications. |
400 |
AS.7029 |
The topic of notification is duplicate. |
The notification subject is duplicate. |
Use a correct notification subject. |
400 |
AS.7030 |
Invalid lifecycle hook default timeout. |
The lifecycle hook timeout duration is invalid. |
Use a valid value. |
400 |
AS.7031 |
Invalid lifecycle hook name. |
The lifecycle hook name is invalid. |
Use a valid value. |
400 |
AS.7032 |
The name of the lifecycle hook is empty. |
The lifecycle hook name is empty. |
Add a lifecycle hook name. |
400 |
AS.7033 |
Invalid lifecycle hook type. |
The lifecycle hook type is invalid. |
Use a valid value. |
400 |
AS.7034 |
Invalid lifecycle hook callback action result. |
The default callback action of the lifecycle hook is invalid. |
Use a valid value. |
400 |
AS.7035 |
The metadata of the lifecycle hook is too long. |
The length of lifecycle hook metadata exceeds the maximum allowed. |
Use a valid value. |
400 |
AS.7036 |
The lifecycle hook is null. |
The lifecycle hook is empty. |
Use a valid value. |
400 |
AS.7037 |
The type of the lifecycle hook is empty. |
The lifecycle hook type is empty. |
Use a valid value. |
400 |
AS.7038 |
The number of hooks in the AS group exceeds the upper limit. |
The number of lifecycle hooks exceeds the upper limit. |
Add a maximum of five lifecycle hooks. |
400 |
AS.7039 |
The lifecycle hook callback action result is empty. |
The lifecycle hook callback action is empty. |
Use a valid value. |
400 |
AS.7040 |
The lifecycle hook callback object is empty. |
The lifecycle hook callback object is empty. |
Use a valid value. |
400 |
AS.7041 |
The lifecycle hook callback object is empty. |
The lifecycle hook name already exists. |
Use a valid value. |
400 |
AS.7042 |
The lifecycle hook callback object does not exist. |
The lifecycle hook callback object does not exist. |
Use a valid value. |
400 |
AS.7043 |
The lifecycle hook topic urn does not exist. |
The notification subject configured for your lifecycle hook does not exist. |
Use a valid value. Check the notification subject configured for your lifecycle hook. |
400 |
AS.7046 |
The tags in the resource is invalid. |
The tag is invalid. |
Use a valid tag. |
400 |
AS.7052 |
The matches in the resource is invalid. |
The matches value is invalid. |
Use a valid matches value. |
400 |
AS.7054 |
The value of tag cannot be duplicate. |
A key in the tag has duplicate values. |
Check and change the duplicate values in the tag. |
400 |
AS.7055 |
The metadata of the lifecycle hook has special character. |
The lifecycle hook metadata contains invalid characters. |
Use a valid value. |
400 |
AS.7111 |
Insufficient instance quota. |
Insufficient ECS quota. |
Release idle ECSs or increase the ECS quota. |
400 |
AS.7112 |
Insufficient volume quota. |
Insufficient EVS disk quota. |
Release idle ECSs or increase the EVS disk quota. |
400 |
AS.7113 |
Insufficient elastic ip quota. |
Insufficient EIP quota. |
Release idle EIPs or increase the EIP quota. |
400 |
AS.7114 |
Insufficient ram quota. |
Insufficient ECS memory quota. |
Release idle ECSs or increase the ECS memory quota. |
400 |
AS.7115 |
Insufficient cpu quota. |
Insufficient ECS vCPU quota. |
Release idle ECSs or increase the ECS vCPU quota. |
400 |
AS.9001 |
The format of the start time of the scaling activity log is incorrect. |
The format of the start time of the scaling log is incorrect. |
Use a valid value. |
400 |
AS.9002 |
The format of the end time for the scaling action log is incorrect. |
The format of the end time for the scaling log is incorrect. |
Use a valid value. |
400 |
AS.9003 |
The value of parameter start_number in the request for the scaling activity log is invalid. |
The start_number in the request for the scaling log is invalid. |
Use a valid value. |
400 |
AS.9004 |
The value of parameter limit in the request for the scaling activity log is invalid. |
The limit in the request for the scaling log is invalid. |
Use a valid value. |
400 |
AS.9005 |
The value of parameter log_id in the request for the scaling log is invalid. |
The logId in the request for the scaling log is invalid. |
Use a valid value. |
400 |
AS.9012 |
The value of parameter type in the request for the scaling activity log is invalid. |
The type in the request for the scaling action log is invalid. |
Use a valid type value. |
400 |
AS.9013 |
The value of parameter status in the request for the scaling activity log is invalid. |
The status in the request for the scaling action log is invalid. |
Use a valid value. |
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