HTTP Status Codes for Dedicated Load Balancers¶
The following code descriptions are only suitable for dedicated load balancers.
Status Code | Type | Description |
|---|---|---|
200 | OK | Normal response to GET and PUT requests. |
201 | Created | Normal response to POST requests. |
204 | No Content | Normal response to DELETE requests. |
Module | Status Code | Type | Error Code | Possible Cause |
|---|---|---|---|---|
Public | 400 | Bad request | ELB.8902 | Malformed request URI or body. |
Invalid admin _state_up value. | ||||
Invalid parameters. | ||||
Batch operations are not allowed. | ||||
Failed to verify the parameters. | ||||
Incorrect request method, for example, updating attributes that can be specified during creation only. | ||||
The network is not external (the value of router:external is set to false). | ||||
The IaaS OpenStack network port has no floating IP address bound. | ||||
The requested floating IP address is not in the IP address range of the external network. | ||||
Invalid fixed IP address. | ||||
The router port does not have a fixed IP address. | ||||
The subnet for the router interface must have a gateway IP address. | ||||
401 | Unauthorized | SYS.0401 | Authentication required. | |
403 | Forbidden | ELB.8903 | The URI does not exist. The resource cannot be found. | |
SYS.0403 | Authentication required. | |||
404 | Not Found | ELB.8904 | The URI does not exist. | |
The resource cannot be found. | ||||
The port UUID is not valid. | ||||
409 | Conflict | ELB.8907 | The port is already in use. | |
The IP address is already in use. | ||||
The IP address pool cannot contain gateway and broadcast addresses. | ||||
The requested floating IP address is already in use. | ||||
The internal IaaS OpenStack network port and fixed IP address are already associated with another floating IP addresses. | ||||
ELB.8905 | The quota is used up. | |||
500 | Internal server error | ELB.8906 | Internal IaaS OpenStack network error. | |
Load balancer | 400 | Bad request | ELB.8931 | The subnet IP version is not the same. |
ELB.8932 | IPv6 subnets are not supported, but the value of ipv6_vip_virsubnet_id is not null. | |||
Backend server | 400 | Bad request | ELB.8933 | IPv6 subnets are not supported, but backend servers use IPv6 addresses. |