HCP Tenant Management Help
The table below describes HTTP status codes that can be returned in response to a request to complete a multipart upload. For more information about HTTP status codes and the error codes that can accompany them, see Error codes.
Code | Meaning | Description |
---|---|---|
200 | OK |
HCP successfully started processing the request. To determine whether the multipart upload was successfully completed, check whether HCP returned a response body that identifies the resulting multipart object or an error response body. |
400 | Bad Request |
Possible reasons include: •The request does not include a Content-Type header. •The XML in the request body is malformed or contains an invalid value. •The request includes a custom metadata (x-amz-meta-) header. |
403 | Forbidden |
Possible reasons include: •The request specifies anonymous access. Only an authenticated user can complete a multipart upload. •The credentials provided with the request are invalid. •The credentials provided with the request do not match the credentials used to initiate the multipart upload. •You do not have permission to complete multipart uploads in the specified bucket. •The S3 compatible API is currently disabled for the specified bucket. |
404 | Not Found |
One of these: •The specified multipart upload does not exist. Either the upload ID is invalid, or the multipart upload was aborted or already completed. •The specified bucket does not exist. |
500 | Internal Server Error |
An internal error occurred. If this error persists, contact your tenant administrator. |
503 | Service Unavailable |
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. |
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.