Comment 2 for bug 1387311

I see your point. However, one could argue that the OpenStack Swift implementation is the one that should be fixed. Technically, according to the Swift docs, Ceph Swift is calculating the ETag correctly.

Fundamentally it comes down to the question: should manifest objects treated as a regular, zero-length, object; or treated specially as a DLO object?

It seems to me that since the specific behavior in this situation isn't spelled out in the API spec, then Glance can't really make any assumptions about what the correct behavior should be. By removing the ETag from this request, as well as the associated tests, it would eliminate exposing this implementation difference, which doesn't have any bearing on API compatibility.

I have also opened Ceph bug http://tracker.ceph.com/issues/9973 . I would be happy t open an OS Swift bug as well, to get this on their radar, if people think that would be a productive thing to do.