Error Case
When the request fails with an error, the following HTTP status codes will be returned.
| Code | Description |
|---|---|
| 400 | Indicates that the URI or request body is invalid. |
| 401 | Indicates that the authentication failed. |
| 403 | Indicates that the user does not have the necessary policy to perform the operation. The HTTP status code will be returned. |
| 404 | Indicates that the resource specified by Path cannot be found. |
| 409 | Indicates that a change to the conflicted or invalid state has been requested to the resources that is specified with Path. Example: An attempt is being made to create a resource with the same name as an existing resource. |
| 413 | Indicates that the length of the request line or the size of the request body exceeds the available range. |
| 415 | Indicates that Content-Type Header is not specified or that a value other than application/json is specified. |
| 500 | Indicates an internal error has occurred. |
| 503 | Indicates that the storage device or the operation target resource is in the busy state and cannot accept the request. If you receive this status code, try the request again. |
The following response body will also be returned.
| Item | Description |
|---|---|
| error_code | Error message number, a fixed 4-digit number.
The same error message number that is returned by ETERNUS CLI is used. See also Appendix A "Error Messages/Error Codes" in "CLI User's Guide" for information on how to handle errors. |
| message | Error message. The format is as follows:
"Description (Factor)" "Description" displays descriptive text according to the error message number. "Factor" displays the parameter that caused the error. |
| internal_code | Internal error code. |