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 . However, checking at the upload workflow used by glance and comparing to Swift documentation , 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.  https://tracker.ceph.com/issues/39160  https://docs.openstack.org/swift/latest/api/large_objects.html#dynamic-large-objects Closes-bug: #1824533 Change-Id: I0b563dfcdc30026669fb089c82db8c3df7edc808
Team and repository tags
Glance Store Library
Glance's stores library
This library has been extracted from the Glance source code for the specific use of the Glance and Glare projects.
The API it exposes is not stable, has some shortcomings, and is not a general purpose interface. We would eventually like to change this, but for now using this library outside of Glance or Glare will not be supported by the core team.
- License: Apache License, Version 2.0
- Documentation: https://docs.openstack.org/glance_store/latest/
- Source: http://git.openstack.org/cgit/openstack/glance_store
- Bugs: https://bugs.launchpad.net/glance-store