Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1234635

Summary:	rgw: COPY doesn't preserve Content-Type if object is larger than 512k
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Yehuda Sadeh <yehuda>
Component:	RGW	Assignee:	Yehuda Sadeh <yehuda>
Status:	CLOSED ERRATA	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.3.0	CC:	cbodley, ceph-eng-bugs, flucifre, kbader, mbenjamin, owasserm, sweil, tganguly, tmuthami
Target Milestone:	rc
Target Release:	1.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-16 22:20:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yehuda Sadeh 2015-06-22 21:49:35 UTC

Description of problem:

Copying of an object does not preserve content type if object is > 512k (S3).

Version-Release number of selected component (if applicable):


How reproducible:
always


Steps to Reproduce:
1. Create object > 512k and set content type
2. Copy it using S3 (need to have x-amz-metadata-directive=COPY)
3. Check content type on destination object

Actual results:
Content type not retained

Expected results:
Content type retained

Comment 3 Tanay Ganguly 2015-07-14 05:39:14 UTC

Marking this Bug as Verified, as the content_type is preserved after copying the object.

root@RGW ~]# rpm -qa |grep ceph
ceph-radosgw-0.94.1-15.el7cp.x86_64
ceph-common-0.94.1-15.el7cp.x86_64

Comment 5 errata-xmlrpc 2015-07-16 22:20: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:1240