[JCLOUDS-1582] ETag of the object uploaded via multipart upload does not match the CompleteMPU response from the transient blobstore

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Fix Version/s: 2.4.0
• Component/s: jclouds-blobstore
• Labels: transient
• Assignee: Timur Alperovich
• Reporter: Timur Alperovich
• Created: 02/Aug/21 00:21
• Updated: 05/Aug/21 09:48
• Resolved: 05/Aug/21 09:48

Description

The local transient blobstore returns a correctly computed S3 MPU ETag when completing the upload, but a subsequent GET/HEAD request returns the MD5 of the whole object instead (not matching the ETag in the CompleteMPU response). Ideally, jclouds should store the MPU ETag and return it on GET/HEAD requests.

This behavior also manifests when using the filesystem blobstore if the extended attributes are not supported. In that case, there is nothing jclouds can do.