- Newest
- Most votes
- Most comments
The errors you're encountering indicate issues with a multipart upload to Amazon S3. Here's what's happening:
NoSuchUpload Error (404): This error means the specified multipart upload does not exist. This can occur when:
- The upload ID is invalid
- The multipart upload has been aborted
- The multipart upload has already been completed
- There may have been a timeout or the upload session expired before completion
InvalidPart Error (400): This error indicates that one or more of the parts you're trying to use to complete the multipart upload could not be found. This happens when:
- The part was not successfully uploaded to S3
- The ETag (entity tag) you're providing doesn't match the part's actual ETag
- The part numbers in your completion request don't correspond to actually uploaded parts
To resolve these issues:
- Ensure you're properly initiating the multipart upload and storing the upload ID
- Verify that each part is successfully uploaded before attempting to complete the upload
- Keep track of the ETag returned for each uploaded part - you'll need to provide these when completing the upload
- Make sure part numbers are consecutive and match the parts you actually uploaded
- Complete the multipart upload promptly after uploading all parts to avoid session expiration
- If a multipart upload fails, you may need to abort it and start a new one rather than trying to resume with an invalid upload ID
Check your code to ensure you're properly handling the upload ID from the initiation step and correctly collecting the part numbers and ETags from each part upload before calling the complete multipart upload operation.
Sources
Using multipart uploads with directory buckets - Amazon Simple Storage Service
upload_part_copy - Boto3 1.42.50 documentation
NoSuchUpload - botocore 1.42.50 documentation
UploadPartCopy - Amazon Simple Storage Service
Relevant content
asked 3 years ago
