Bug 1490931

Summary:	Doc for Object Gateway API should be more clear
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Tupper Cole <tcole>
Component:	RGW	Assignee:	Matt Benjamin (redhat) <mbenjamin>
Status:	CLOSED NOTABUG	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.3	CC:	asriram, cbodley, ceph-eng-bugs, jowilkin, kbader, kdreyer, mbenjamin, sweil, tcole
Target Milestone:	rc
Target Release:	3.*
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-06 01:06:48 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 Tupper Cole 2017-09-12 13:57:12 UTC

Description of problem:Doc on Object Gateway API is unclear regarding user create failures. 


Referencing http://tracker.ceph.com/issues/21371

The community doc states that trying to create an existing user should respond 409:

UserExists

Description: Attempt to create existing user.
Code: 409 Conflict


This is not the case- an additional key and secret are added to the uid.

Also, I can't find a current Red Hat reference for the adminops.

Comment 3 John Wilkins 2018-06-04 18:48:06 UTC

There is an existing entry. The admin ops information is in the downstream developer guide here: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/developer_guide/obj-gw-admin-api#create-user

Comment 4 John Wilkins 2018-08-07 16:09:05 UTC

Ken, 

The documentation is correct. The behavior of the API should not allow a user to change the password in this case. It seems to be an issue with the API.

Comment 5 Ken Dreyer (Red Hat) 2018-08-09 21:21:00 UTC

John, would you please clarify "Steps to reproduce", "Actual Results", "Expected Results" for Dev and QE here?