Etag generation in swift3 does not match AWS S3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Swift3 |
In Progress
|
Undecided
|
Unassigned |
Bug Description
I have a report that the etag computation in swift3 does not match the
one in Amazon S3:
* AWS S3 returns MD5(hex(
concatenated to "-N" where N is the number of parts
* swift3 instead returns MD5(MD5_
For the etags of two parts: f4268b057129ad6
ae611f5328ee26e
8dfd4f6217c47b1
multipart upload response. 8dfd4f6217c47b1
computed as:
echo 'f4268b057129ad
For the etags of two parts: 1672170d6afd306
2a1e3a9c4ec7fe8
850b7e0ddbbf389
upload response. Aside from the fact that there is no "-N" suffix,
850b7e0ddbbf389
invocation as before, but it has to be computed as:
echo -n '1672170d6afd30
The etag generation in swift3 should be changed to match the one in
AWS S3.
Changed in swift3: | |
status: | New → Confirmed |
Changed in swift3: | |
status: | Confirmed → In Progress |
Related fix proposed to branch: master /review. openstack. org/302475
Review: https:/