Bug #18936
openrgw slo manifest: etag and size should be optional
0%
Description
In debugging a downstream problem with RGW swift SLO, I found the following apparent (?) issues
1. downloading an SLO whose manifest contains paths which do not resolve, possibly unexpected behavior results--for example, if the last of 4 segments in the manifest cannot be resolved, the object can still retrieved by GET--we return just the first 3 segments
the above may be correct behavior, I didn't see guidance in http://docs.openstack.org/developer/swift/overview_large_objects.html
HOWEVER, the swift doc above clearly states that the "etag" and "size_bytes" attributes are optional, so I expect that if the corresponding "path" values are valid, a correct will be assembled; instead, in RGW, the RGW service reports a correct result, but decodes a stored manifest with etag "" and size_bytes 0, total bytes == 0--and the resulting downloads hang until timeout at the client--ditto for swift stat requests.
Files