ed356fc6b4
While testing glance with Ceph Rados Gateway using latest Ceph release (Nautilus), i've found that glance fails to upload the manifest using dynamic large objects mode because of the value used in ETag request. This issue has been reported to Ceph as it seems related to some recent change in radosgw code [1]. However, checking at the upload workflow used by glance and comparing to Swift documentation [2], I wonder if adding the etag is actually providing any value. In the Swift the ETag header is used to validate integrity when uploading chunks, not the manifest while glance is doing exactly the oposite, not sending the etag in the chunks (I guess to avoid checksuming big images, which makes sense to me) and sending it when puting the manifest. This patch is removing the etag header when sending the PUT request for the manifest in chunked uploads. [1] https://tracker.ceph.com/issues/39160 [2] https://docs.openstack.org/swift/latest/api/large_objects.html#dynamic-large-objects Closes-bug: #1824533 Change-Id: I0b563dfcdc30026669fb089c82db8c3df7edc808 |
||
|---|---|---|
| .. | ||
| etc | ||
| functional | ||
| unit | ||
| __init__.py | ||
| base.py | ||
| fakes.py | ||
| utils.py | ||