Bug 1536795

Summary:	resharding doesn't seem to preserve bucket acls
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Orit Wasserman <owasserm>
Component:	RGW	Assignee:	Orit Wasserman <owasserm>
Status:	CLOSED ERRATA	QA Contact:	Vidushi Mishra <vimishra>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.0	CC:	bhubbard, cbodley, ceph-eng-bugs, edonnell, hnallurv, jbrier, kbader, kdreyer, mbenjamin, owasserm, sweil, tchandra, vimishra
Target Milestone:	rc	Keywords:	TestOnly
Target Release:	3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.4-6.el7cp Ubuntu: ceph_12.2.4-7redhat1xenial	Doc Type:	Bug Fix
Doc Text:	.Resharding a bucket that has ACLs set no longer alters the bucket ACL Previously, in the Ceph Object Gateway (RGW), resharding a bucket with an access control list (ACL) set alters the bucket ACL. With this update to {product}, ACLs on a bucket are preserved even if they are resharded.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-26 18:16:43 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:
Bug Depends On:
Bug Blocks:	1557269, 1584264

Description Orit Wasserman 2018-01-21 10:32:22 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. s3 -us  create publicbucket cannedAcl=public-read-write
2. s3 -us list publicbucket
3. s3 -us getacl publicbucket filename=publicbucket.acl
4. radosgw-admin bucket reshard --bucket=publicbucket --num-shards=10
5. s3 -us getacl publicbucket filename=publicbucket2.acl

Actual results:
bucket acl are not the same

Expected results:
bucket acl unchanged

Additional info:

Comment 4 Orit Wasserman 2018-04-25 06:59:16 UTC

upstream luminous fix:
https://github.com/ceph/ceph/pull/20327

Comment 11 errata-xmlrpc 2018-09-26 18:16:43 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-2018:2819