Bug 1704901

Summary:	[RFE] RGW renaming a user
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vikhyat Umrao <vumrao>
Component:	RGW	Assignee:	shilpa <smanjara>
Status:	CLOSED ERRATA	QA Contact:	RUDRA PRATAP <rpratap>
Severity:	medium	Docs Contact:	Bara Ancincova <bancinco>
Priority:	medium
Version:	3.2	CC:	agunn, cbodley, ceph-eng-bugs, ceph-qe-bugs, jgalvez, kbader, mbenjamin, mhackett, roemerso, rpratap, smanjara, sweil, tchandra, tserlin, vpoliset
Target Milestone:	z1	Keywords:	FutureFeature
Target Release:	3.3
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.12-68.el7cp Ubuntu: ceph_12.2.12-61redhat1	Doc Type:	Enhancement
Doc Text:	.Renaming users is now supported This update of {product} adds the ability to rename the Ceph Object Gateway users. For details, see the _Rename a User_ section in the Object Gateway Guide for link:{object-gw-rhel-guide}#rename-a-user-rgw[Red Hat Enterprise Linux] or for link:{object-gw-ubuntu-guide}#rename-a-user-rgw[Ubuntu].	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 13:29:00 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:	1725227, 1726135, 1733598

Description Vikhyat Umrao 2019-04-30 18:37:45 UTC

Description of problem:
[RFE] RGW renaming a user

Requesting a new command to implement RGW user rename. something like:

radosgw-admin user rename --uid=<existing username> --new-uid=<new username>


Version-Release number of selected component (if applicable):
Red Hat Ceph Storage 3.2

Comment 15 Matt Benjamin (redhat) 2019-06-28 18:52:01 UTC

*** Bug 1673831 has been marked as a duplicate of this bug. ***

Comment 21 Giridhar Ramaraju 2019-08-05 13:11:32 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 22 Giridhar Ramaraju 2019-08-05 13:12:30 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 27 shilpa 2019-08-19 07:31:12 UTC

Hi Subhash,

Here are the steps to verify 'user rename':

1. Create a user 'user1'.
2. Create a subuser under 'user1' to test swift access.
2. Create buckets/objects with 'user1' permission
3. Rename 'user1' to a desired name, say 'user2' (this step takes a while depending on the number of objects present)

 # radosgw-admin user rename --uid user1 --new-uid user2

4. Verify if the user has been successfully renamed by checking 'user info --uid user2'. The S3 and swift access/secret keys should not have changed.
5. 'user1' should not exist anymore.
6. Run GET/PUT operations on the existing buckets and objects which now belong to 'user2'.

You could also run some negative tests like specifying an already existing user name in '--new-uid'.

Comment 50 errata-xmlrpc 2019-10-22 13:29:00 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-2019:3173

Comment 51 Red Hat Bugzilla 2023-09-18 00:16:09 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days