Bug 1213989 - RGW Swift API: lack of mandatory ETag header in response for COPY/PUT with X-Copy-From
Summary: RGW Swift API: lack of mandatory ETag header in response for COPY/PUT with X-...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 1.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 1.3.0
Assignee: Yehuda Sadeh
QA Contact: Harish NV Rao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-21 17:21 UTC by Yehuda Sadeh
Modified: 2022-02-21 18:35 UTC (History)
10 users (show)

Fixed In Version: ceph-0.94.1-7.el7cp
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-24 15:52:12 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 11087 0 None None None Never
Red Hat Issue Tracker RHCEPH-3487 0 None None None 2022-02-21 18:35:51 UTC
Red Hat Product Errata RHBA-2015:1183 0 normal SHIPPED_LIVE Ceph bug fix and enhancement update 2015-06-24 19:49:46 UTC

Description Yehuda Sadeh 2015-04-21 17:21:54 UTC 
Description of problem:


No ETag header in a response for swift copy operation


How reproducible:
always

Steps to Reproduce:
1. Copy an object through the swift api

Actual results:
No ETag header


Expected results:
ETag header

Additional info:
Fixed upstream
Comment 3 shilpa 2015-06-15 14:03:48 UTC 
Verified in  ceph-0.94.1-11. COPY operation has Etag header in response:

# curl -i http://10.x.x.x/swift/v1/test-bucket/yum_save_tx -X COPY -H "X-Auth-Token: AUTH_rgwtkxxx" -H "Destination: test-container/yum_save"

HTTP/1.1 201 Created
etag: c11fe4f67215e8cad987d68a0d2e86c2
Last-Modified: Mon, 15 Jun 2015 13:59:13 GMT
X-Copied-From: test-bucket/yum_save_tx.2015-06-15.06-41.F0cSTk.yumtx
X-Copied-From-Account: testuser
X-Copied-From-Last-Modified: Mon, 15 Jun 2015 12:39:49 GMT
Content-type: binary/octet-stream
Content-Length: 0
Comment 5 errata-xmlrpc 2015-06-24 15:52:12 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2015:1183
Note You need to log in before you can comment on or make changes to this bug.