Every error response body contains an error code and a message that provides more information about the error. Error codes are returned in addition to HTTP status codes. A single HTTP status code can correspond to multiple error codes.
The table below describes the error codes that can be returned in response to HS3 requests. For information on the HTTP status codes returned in response to specific requests, see the individual request descriptions in Working with buckets and Working with objects.
Error code | Description | HTTP status code |
---|---|---|
AccessDenied |
One of: •You do not have permission to perform the requested operation. • The user account identified by the access key provided in the request is disabled. To have the account enabled, contact your tenant administrator. • The target bucket does not currently support the requested operation. •The tenant does not currently support use of the HS3 API. •You are using a presigned URL, and the time period during which the URL was valid has expired. |
403 Forbidden |
BadDigest |
One of: •The value of the Content-MD5 header does not match the Base64-encoded 128-bit MD5 hash of the submitted data. •The value of the Content-MD5 header is not a valid hash value. |
400 Bad Request |
BucketAlreadyExists | You are trying to create a bucket, but a bucket with the specified name already exists and either is owned by a user other than you or has no owner. | 409 Conflict |
BucketAlready OwnedByYou |
You are trying to create a bucket, but a bucket with the specified name already exists and is owned by you. | 200 OK |
BucketNotEmpty | You are trying to delete a bucket that is not empty. | 409 Conflict |
InvalidAccessKeyId | The access key provided in the request does not correspond to a valid user account. | 403 Forbidden |
InvalidArgument |
One of: •A query parameter has an invalid value. •An ACL grant header specifies an invalid grantee. •The request includes conflicting conditional headers (for example, If-Match and If-None-Match). |
400 Bad Request |
InvalidBucketName | The specified bucket name is invalid. | 400 Bad Request |
InvalidBucketState |
One of: •The target bucket does not currently support the requested operation. •The tenant does not currently support use of the HS3 API. |
409 Conflict |
InvalidRange |
You are trying to retrieve part of an object, and one of these is true: •The specified start position is greater than the size of the requested data. •The size of the specified range is zero. |
416 Requested Range Not Satisfiable |
InvalidRequest |
You are trying to create a bucket, and one of these is true: •You already own the maximum number buckets allowed per user. •The tenant does not have enough space for another bucket. •The tenant already has the maximum number of buckets it’s allowed to have. •An unexpected error occurred. |
400 Bad Request |
InternalError |
An internal error occurred. Try the request again, gradually increasing the delay between each successive attempt. If this error persists, contact your tenant administrator. |
500 Internal Server Error |
KeyTooLong | The specified object name is too long. | 400 Bad Request |
MalformedXML |
The request is invalid. Possible reasons include: •The object name specified in the request is invalid. •A query parameter specifies an invalid value. •The request includes both the x-amz-acl header and an individual ACL grant header. •The XML in the request body is malformed or contains invalid values. |
400 Bad Request |
MetadataTooLarge | The custom metadata you are trying to store is larger than two KB. | 400 Bad Request |
MethodNotAllowed | The requested HTTP method is not supported for the target tenant, bucket, or object. | 405 Method Not Allowed |
NoSuchBucket | The specified bucket does not exist. | 404 Not Found |
NoSuchKey | HCP could not find an object with the specified name. | 404 Not Found |
NotImplemented | The requested operation is not supported. | 501 Not Implemented |
OperationAborted |
One of: •HCP cannot perform the requested operation because a conflicting operation is already in progress. •You are trying to delete an object that is under retention. •You are trying to create an object with the same name as an existing object, and versioning is disabled. •You are trying to read, add an ACL to, or delete an object that is currently being written to the bucket. |
409 Conflict |
OutOfSpace | The object you are trying to store or the custom metadata you are trying to add is too big for the amount of space left in the bucket. | 413 Request Entity Too Large |
PreconditionFailed | HCP did not perform the requested operation because a specified precondition for the operation was not satisfied. | 304 Not Modified or 412 Precondition Failed |
ServiceUnavailable |
HCP is temporarily unable to handle the request, probably due to system overload, maintenance, or upgrade. Try the request again, gradually increasing the delay between each successive attempt. If this error persists, contact your tenant administrator. |
503 Service Unavailable |
SignatureDoesNotMatch | The signature provided with the request does not match the request contents. Check that the secret key and signing method used are correct. | 403 Forbidden |
© 2016 Hitachi Data Systems Corporation. All rights reserved.