Error Codes
Context
- An error code returned by an API does not correspond to one error message. The following table lists only common error messages.
- Most BMS APIs are asynchronous. Some error codes are displayed in the returned messages for task viewing requests. HTTP status codes may not be accurate.
- The BMS service is strongly dependent on other services, such as network and storage. When error messages are provided for the BMS-depended services, contact technical support for troubleshooting.
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 API Gateway Error Codes.
|
Status Code |
Error Code |
Error Message |
Description |
Handling Measure |
|---|---|---|---|---|
|
400 |
BMS.0001 |
Fail to parse request, reason: %s. |
Request error. |
Check the request body according to the returned error message. |
|
400 |
BMS.0002 |
The BMS service is unavailable. |
BMS has not been launched. |
Select a region where the BMS service is available. |
|
400 |
BMS.0003 |
Create BareMetal Server error, request is null. |
Request error. |
Check the request body according to the returned error message. |
|
400 |
BMS.0004 |
Role check fail, reason: %s. |
Insufficient permission. |
See the returned error message or contact technical support. |
|
400 |
BMS.0005 |
Role check fail, reason: You do not have permission or your balance is insufficient. |
Insufficient permission. |
See the returned error message or contact technical support. |
|
400 |
BMS.0008 |
Fail to query flavor [%s], reason: %s. |
Failed to query a flavor. |
See the returned error message or contact technical support. |
|
400 |
BMS.0006 |
Fail to operate baremetal server. |
Failed to create the task. |
See the returned error message or contact technical support. |
|
400 |
BMS.0009 |
Fail to query flavor extra specs[%s], reason: %s. |
Failed to query flavor attributes. |
See the returned error message or contact technical support. |
|
400 |
BMS.0010 |
Fail to query image [%s], reason: %s. |
Failed to query an image. |
See the returned error message or contact technical support. |
|
400 |
BMS.0011 |
The selected images cannot be used to apply for BMSs, %s. |
The images do not support BMS. |
See the returned error message or contact technical support. |
|
400 |
BMS.0012 |
The number of IP addresses in the selected subnet[%s] is insufficient. |
Insufficient IP addresses in the selected subnet. |
Check whether the IP addresses of the subnet are used up. |
|
400 |
BMS.0013 |
Fail to query ports by subnet [%s], reason: %s. |
Failed to query the port. |
See the returned error message or contact technical support. |
|
400 |
BMS.0014 |
The specified IP address conflicts with an existing IP address in subnet[%s]. |
IP address conflict. |
Modify the NIC IP address. |
|
400 |
BMS.0015 |
Fail to query subnet, reason: %s. |
Failed to query the NIC. |
See the returned error message or contact technical support. |
|
400 |
BMS.0017 |
The number[%d] of EIPs has reached the maximum[%d] allowed. Apply for a higher quota and try again. |
The EIP quota is insufficient. |
Apply for a higher EIP quota. |
|
400 |
BMS.0218 |
Fail to create order, reason: %s. |
Failed to create the order. |
See the returned error message or contact technical support. |
|
400 |
BMS.0219 |
OpenStack nova change ServerName fail. |
Failed to change the BMS name. |
Contact technical support. |
|
400 |
BMS.0018 |
Request parameter is invalid. |
Invalid request parameters. |
Modify the request parameters based on the returned error message. |
|
400 |
BMS.0019 |
publicIp parameter is illegal, reason: %s. |
Invalid NIC parameters. |
See the returned error message or contact technical support. |
|
400 |
BMS.0020 |
Fail to check chargingMode, reason: %s. |
Failed to check the billing mode. |
See the returned error message or contact technical support. |
|
400 |
BMS.0021 |
Flavor parameter is illegal, reason: %s. |
The flavor is invalid for creating the BMS. Select another flavor. |
Select a valid flavor. |
|
400 |
BMS.0022 |
Request parameter is invalid. |
Invalid request parameters. |
Modify the request parameters based on the returned error message. |
|
400 |
BMS.0023 |
Fail to query limits, reason: %s |
Failed to query the quota. |
See the returned error message or contact technical support. |
|
400 |
BMS.0025 |
The number of cloud servers has reached the maximum allowed. |
The number of BMSs exceeds the quota. |
Apply for a higher quota. |
|
400 |
BMS.0026 |
The number of CPU cores used by all cloud servers has reached the maximum allowed. |
The number of BMS CPUs exceeds the quota. |
Apply for a higher quota. |
|
400 |
BMS.0027 |
The memory space used by all cloud servers has reached the maximum allowed. |
The BMS memory exceeds the quota. |
Apply for a higher quota. |
|
400 |
BMS.0028 |
The number of CPU cores used by all cloud servers and that of cloud servers have reached the maximum allowed. |
The number of BMSs and that of CPUs exceed the quotas. |
Apply for a higher quota. |
|
400 |
BMS.0029 |
The memory space used by all cloud servers and the number of cloud servers have reached the maximum allowed. |
The number of BMSs and the memory exceed the quotas. |
Apply for a higher quota. |
|
400 |
BMS.0030 |
The memory space and number of CPU cores used by all cloud servers have reached the maximum allowed. |
The BMS memory and the number of CPUs exceed the quotas. |
Apply for a higher quota. |
|
400 |
BMS.0031 |
The number of cloud servers, the memory space used by all cloud servers, and the number of CPU cores used by all cloud servers have reached the maximum allowed. |
The number of BMSs, the number of CPUs, and the memory exceed the quotas. |
Apply for a higher quota. |
|
400 |
BMS.0032 |
Token check fail. |
Contact technical support to apply for a BMS. |
See the returned error message or contact technical support. |
|
403 |
BMS.0033 |
Fail to check roles, reason: %s. |
You do not have operation rights. Contact technical support. |
See the returned error message or contact technical support. |
|
400 |
BMS.0034 |
Not support create Bare Metal Server. |
Currently, BMSs cannot be automatically provisioned. |
This operation is not supported. |
|
400 |
BMS.0047 |
Root volume is illegal, reason: %s. |
Invalid system disk. |
See the returned error message or contact technical support. |
|
400 |
BMS.0049 |
Query keypair fail, reason is: %s. |
Failed to query key_name. |
See the returned error message or contact technical support. |
|
400 |
BMS.0089 |
The tag policy does not allow the specified value for the following tag key: %s. |
Failed to pass the verification of tag policy compliance. |
Change the tag values according to the policy or contact technical support. |
|
400 |
BMS.0102 |
The image does not support attach volume. |
This image does not support volume attaching. |
Contact technical support. |
|
400 |
BMS.0103 |
Attach volume %s fail, volume info is null. |
The disk does not exist. |
Check whether the disk information is correct. |
|
400 |
BMS.0104 |
Attach volume %s fail, data volume can not attach in root volume device. |
The data volume cannot be attached to the mount point of the system volume. |
Select another mount point. |
|
400 |
BMS.0105 |
Attach volume %s fail, device is illegal. |
The mount point is invalid. |
Check whether the mount point is valid. |
|
400 |
BMS.0106 |
Attach volume %s fail, volume's az is not equal with server's az. |
The AZ of data disks is different from that of the BMS. |
Ensure that the AZ of data disks is the same as that of the BMS. |
|
400 |
BMS.0108 |
Attach volume %s fail, root volume does not match the VM, do not change image. |
The system disk does not match the BMS. |
Attach a matching system disk to the BMS. |
|
400 |
BMS.1001 |
Volume can only be attached when server %s stopped or active. |
This operation can be performed only when the BMS is in running or stopped. |
Try again later or contact technical support. |
|
400 |
BMS.1002 |
Attach volume fail, server %s attchment num over limit. |
The number of data disks that can be attached to the BMS exceeds the quota. |
Contact technical support. |
|
400 |
BMS.1003 |
Attach shareable volume %s fail, volume status is %s, not available or inuse. |
The disk status is invalid. |
Check whether the disk is in attached or other unavailable status. |
|
400 |
BMS.1004 |
Attach shareable volume %s fail, volume status is %s, not available or inuse. |
The number of shared data disks that can be attached to the BMS exceeds the quota. |
Contact technical support. |
|
400 |
BMS.1006 |
Server %s info is null or its status or its metadata is null. |
The running status of the BMS cannot be obtained. |
Try again later or contact technical support. |
|
400 |
BMS.1007 |
Calling interface failed |
Failed to call the API. |
See the returned error message or contact technical support. |
|
400 |
BMS.1008 |
The server[%s] is not HANA server, volume[%s] does not match the server. |
The disk type does not match the BMS. |
Check whether the disk type matches the BMS or contact the technical support. |
|
400 |
BMS.1009 |
Attach shareable volume %s fail, volume status is %s, the volume has been attached to the server. |
The data disk has been attached to the BMS. |
Select another data disk. |
|
400 |
BMS.1011 |
Attach shareable volume %s fail, volume status is %s, not available or inuse. |
The data disk is being attached. |
Do not repeatedly attach the data disk. |
|
400 |
BMS.3001 |
Query security group failed: %s. or Query vpcId for subnet failed: %s. |
Failed to query the security group or subnet. |
See the returned error message or contact technical support. |
|
400 |
BMS.3011 |
Decoded token is null. |
System error. |
See the returned error message or contact technical support. |
|
400 |
BMS.3025 |
Not support create shareable data volumes. |
The EVS disk type is incorrect. |
See the returned error message or contact technical support. |
|
400 |
BMS.3035 |
Attach volume fail: the bmsid [%s] in volume metadata is not the same with bmsid [%s] in url. |
No matching disk is found for the BMS. |
Ensure that the disk matches the BMS or contact technical support. |
|
400 |
BMS.3039 |
The password is illegal, reason: %s. |
Failed to verify password complexity. |
See the password rules. |
|
400 |
BMS.0246 |
The vpcId[%s] is invalid or not-existing. |
Failed to query the VPC. |
See the returned error message or contact technical support. |
|
400 |
BMS.0201 |
Fail to check the baremetal server params, reason: %s. |
The parameters for creating the BMS are incorrectly configured. |
See the returned error message or contact technical support. |
|
400 |
BMS.0202 |
All volumes must be in same type. |
The data disk type is invalid. |
See the returned error message or contact technical support. |
|
400 |
BMS.0203 |
Volume is illegal, %s. |
Parameter Volume is invalid. |
See the returned error message or contact technical support. |
|
400 |
BMS.0204 |
The num of datavolume is illegal, the num is %d, max num allow is %d. |
The number of data disks exceeds the upper limit. |
See the returned error message or contact technical support. |
|
400 |
BMS.0205 |
The number of baremetal servers is out of range for one quest. |
The BMS quantity is invalid. |
Change or delete the BMS quantity. |
|
400 |
BMS.0206 |
The baremetal server name [%s] is include invalid char. |
The name contains invalid characters. |
Change the name as prompted. |
|
400 |
BMS.0207 |
VPC is illegal, reason: %s. |
No IP address can be specified when BMSs are created in a batch. |
See the returned error message or contact technical support. |
|
400 |
BMS.0208 |
Fail to get RegionInfo by tenant [%s], reason: %s. |
Failed to query the AZ. |
See the returned error message or contact technical support. |
|
400 |
BMS.0210 |
The size of userdata [%d] is over quota limits [%d]. |
The length of the injected data exceeds the upper limit. |
Modify the injected data. |
|
400 |
BMS.0211 |
The image platform is [%s], support publicKey, reason: the publicKey is illegal, null is not allowed. |
Invalid key. |
Select a valid key. |
|
400 |
BMS.0114 |
Volume %s is not in server %s attach volume list. |
The disk to be detached is not in the disk list of the BMS. |
Check whether the disk exists. |
|
400 |
BMS.0212 |
System is overloaded, please try again later. |
The system is overloaded. |
Try again later. |
|
400 |
BMS.0213 |
OBTAZ role verify fail: not allowed role. |
Insufficient permission. |
See the returned error message or contact technical support. |
|
400 |
BMS.0214 |
Query subnet[%s] failed: response is null. |
Failed to query the NIC. |
See the returned error message or contact technical support. |
|
400 |
BMS.0215 |
The response of inquiry order info is null or invalid. |
Failed to create the order. |
See the returned error message or contact technical support. |
|
400 |
BMS.0216 |
Submit order[%s] failed: %s. |
Failed to submit the order. |
See the returned error message or contact technical support. |
|
400 |
BMS.0217 |
Create server fail, reason: metaData is illegal. |
Failed to verify metadata. |
See the returned error message or contact technical support. |
|
400 |
BMS.0222 |
primary port can not be deleted. |
The primary NIC cannot be deleted. |
See the returned error message or contact technical support. |
|
400 |
BMS.0223 |
Only SCSI disks are supported. |
Currently, only SCSI disks are supported. |
Select the SCSI disk type. |
|
400 |
BMS.0039 |
Server is stopped, not allow to stop. |
The BMS has been shut down. |
Do not stop the BMS again. |
|
400 |
BMS.0040 |
The server does not exist. |
The BMS does not exist. |
See the returned error message or contact technical support. |
|
400 |
BMS.0035 |
Server is powering on, not allow to %s. |
The BMS is being powered on and no other operations are allowed. |
See the returned error message or contact technical support. |
|
400 |
BMS.0036 |
Server is powering off, not allow to %s. |
The BMS is being powered off and no other operations are allowed. |
See the returned error message or contact technical support. |
|
400 |
BMS.0038 |
Server is running, not allow to start. |
The BMS is running and cannot be started. |
Do not start the BMS again. |
|
400 |
BMS.0037 |
Server is rebooting, not allow to %s. |
The BMS is being restarted and no other operations are allowed. |
See the returned error message or contact technical support. |
|
403 |
BMS.0288 |
Policy doesn't allow %s to be performed. |
You do not have permissions to perform this operation. |
See the returned error message or contact technical support. |
|
400 |
BMS.0290 |
Batch attach volume type must be sharable. |
The disk is not a shared disk and cannot be attached to multiple BMSs. |
Select a shared disk. |
|
400 |
BMS.0291 |
enterprise_project_id can not be empty. |
The enterprise project ID cannot be empty. |
See the returned error message or contact technical support. |
|
400 |
BMS.0294 |
Query enterprise_project_id[%s] failed %. |
Failed to invoke EPS to query the project. |
See the returned error message or contact technical support. |
|
400 |
BMS.0293 |
Query enterprise_project_id[%s] failed: response is null. |
Failed to query the project information. |
See the returned error message or contact technical support. |
|
400 |
BMS.0292 |
enterprise_project_id[%s] is deactive. |
The enterprise project has been suspended. |
See the returned error message or contact technical support. |
|
400 |
BMS.0071 |
Using an existing EIP and creating a new EIP can't be used at the same time. |
If an EIP has been specified for creating the BMS, no other EIP can be created for the BMS. |
See the returned error message or contact technical support. |
|
400 |
BMS.0072 |
An existing EIP cannot be assigned to the ECSs created in batches. |
An EIP cannot be used to create multiple BMSs. |
See the returned error message or contact technical support. |
|
400 |
BMS.0073 |
Bandwidth info in eip is null. |
The bandwidth parameter is empty. |
See the returned error message or contact technical support. |
|
400 |
BMS.0074 |
Parameter exetendparam or chargingMode is null. |
The EIP extension parameter is unavailable. |
See the returned error message or contact technical support. |
|
400 |
BMS.0075 |
Bandwidth info in eip is null. |
The bandwidth ID is empty. |
See the returned error message or contact technical support. |
|
400 |
BMS.0076 |
Parameter chargingMode only supports postPaid when shared type is whole. |
The EIP billing mode is unavailable. |
See the returned error message or contact technical support. |
|
400 |
BMS.0077 |
PublicIp parameter is illegal, reason: %s. |
Invalid bandwidth size. |
See the returned error message or contact technical support. |
|
400 |
BMS.0078 |
Shared bandwidth has been bound to %d EIPs, quota is %d. |
EIP quota is insufficient. |
See the returned error message or contact technical support. |
|
400 |
BMS.0079 |
Specifies the bandwidth of the shared type and the id cannot be empty. |
The EIP bandwidth type is unavailable. |
See the returned error message or contact technical support. |
|
400 |
BMS.0080 |
Check subnet status failed. |
The subnet status is unavailable. |
Check whether the subnet exists or whether it is in ACTIVE state. |
|
400 |
BMS.0297 |
Fail to attach volume[%s]: volume is locked. |
The submitted EVS disk order has not been paid. The EVS disk cannot be attached to or detached from the BMS. |
See the returned error message or contact technical support. |
|
400 |
BMS.0054 |
Check capacity fail, the number of capacity is: [%d], and req num is: [%d]. |
Failed to verify the capacity. |
The capacity is insufficient. Contact technical support. |
|
400 |
BMS.0055 |
Query capacity fail, Flavor id is [%s], reason: [%s]. |
Failed to query the quota. |
See the returned error message or contact technical support. |
|
400 |
BMS.2005 |
Network could not be found. |
Failed to query the network. |
Check the network information or contact technical support. |
|
400 |
BMS.3037 |
Insufficient resources or failed to start the BMS. |
Insufficient resources or failed to start the BMS. |
Contact technical support. |
|
400 |
BMS.3004 |
Failed to create the BMS due to an internal system error. |
Failed to create the BMS due to an internal system error. |
Contact technical support. |
|
400 |
BMS.3005 |
Failed to create the port. |
Failed to create the port. |
Contact technical support. |
|
400 |
BMS.3033 |
Failed to create the system disk. |
Failed to create the system disk. |
Contact technical support. |
|
400 |
BMS.3029 |
Failed to create the system disk. The disk status is abnormal. |
Failed to create the system disk. The disk status is abnormal. |
Contact technical support. |
|
400 |
BMS.3006 |
Failed to assign the floating IP address. |
Failed to assign the EIP. |
Contact technical support. |
|
400 |
BMS.3021 |
Failed to create the data disk. |
Failed to create the data disk. |
Contact technical support. |
|
400 |
BMS.3019 |
Failed to attach the data disk. |
Failed to attach the data disk. |
Contact technical support. |
|
400 |
BMS.3038 |
Failed to assign the EIP. |
Failed to assign an EIP. |
Contact technical support. |
|
400 |
BMS.0315 |
Disks cannot be attached to a BMS using this flavor[%s]. |
Disks cannot be attached to a BMS using this flavor. |
See the returned error message or contact technical support. |
|
400 |
BMS.0316 |
RAID level and RAID type do not match. |
The RAID level does not match the RAID type. |
See the returned error message or contact technical support. |
|
400 |
BMS.0317 |
Disk information is empty. |
Disk information is empty. |
See the returned error message or contact technical support. |
|
400 |
BMS.0320 |
This flavor does not support RAID formed by disks of this type. |
This flavor does not support RAID formed by disks of this type. |
See the returned error message or contact technical support. |
|
400 |
BMS.0321 |
This flavor does not support RAID formed by disks of this size. |
This flavor does not support RAID formed by disks of this size. |
See the returned error message or contact technical support. |
|
400 |
BMS.0322 |
Disk quantity and RAID level do not match. |
Disk quantity and RAID level do not match. |
See the returned error message or contact technical support. |
|
400 |
BMS.0323 |
Disk quantity does not match that in the flavor. |
Disk quantity does not match that in the flavor. |
See the returned error message or contact technical support. |
|
400 |
BMS.0325 |
Disk quantity exceeds that supported by the flavor. |
Disk quantity exceeds that supported by the flavor. |
See the returned error message or contact technical support. |
|
400 |
BMS.0327 |
Only JBOD is supported. |
Only JBOD is supported. |
See the returned error message or contact technical support. |
|
400 |
BMS.0328 |
Only single-disk RAID 0 is supported. |
Only single-disk RAID 0 is supported. |
See the returned error message or contact technical support. |
|
400 |
BMS.0329 |
Disk type is empty. |
Disk type is empty. |
See the returned error message or contact technical support. |
|
400 |
BMS.0330 |
RAID is not supported. |
RAID is not supported. |
See the returned error message or contact technical support. |
|
400 |
BMS.0331 |
No IPv6 Open Beta Test permissions. |
No IPv6 Open Beta Test permissions. |
See the returned error message or contact technical support. |
|
400 |
BMS.0333 |
IPv6 is not supported. |
IPv6 is not supported. |
See the returned error message or contact technical support. |
|
400 |
BMS.0400 |
the image[%s] is not support IPv6. |
The image does not support IPv6. |
See the returned error message or contact technical support. |
|
400 |
BMS.0360 |
This operation cannot be performed because EVS Disk %s is frozen. |
The disk has been frozen and cannot be operated for the BMS. |
See the returned error message or contact technical support. |
|
400 |
BMS.3026 |
Password does not meet the requirements of the rule. |
The password does not meet requirements. |
See the returned error message or contact technical support. |
|
400 |
BMS.3027 |
VPC parameter is illegal. |
Invalid VPC parameters. |
See the returned error message or contact technical support. |
|
400 |
BMS.3028 |
cinder quota check fail. |
Disk quota is abnormal. |
See the returned error message or contact technical support. |
|
400 |
Common.0018 |
tenantId in token is not the same with in URL. |
tenant_id in the token is different from that in the URL. |
Check whether the tenant token is correct. |
|
400 |
BMS.0111 |
none or multiple passwords specified, please specify one. |
Password or key pair is not specified, or both specified. |
The password and key pair cannot be specified at the same time. Select one of them based on the login mode. |
|
400 |
BMS.0395 |
The server[%s] is windows system and can not support remote login. |
Windows BMSs do not support remote login. |
See the returned error message or contact technical support. |
|
400 |
BMS.0605 |
the BMS is locked. |
The BMS is locked. |
See the returned error 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.