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 1680100

Summary:	RGW pool documentation is out of date.
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Tupper Cole <tcole>
Component:	Documentation	Assignee:	Ranjini M N <rmandyam>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tejas <tchandra>
Severity:	high	Docs Contact:	Aron Gunn <agunn>
Priority:	unspecified
Version:	3.1	CC:	agunn, asriram, assingh, hyelloji, jbrier, kdreyer, mmanjuna
Target Milestone:	rc
Target Release:	4.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-13 06:49:39 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 2019-02-22 17:24:51 UTC

Description of problem: In Luminous/RHCS 3.0 the pools needed for Ceph Object Gateway changed. This is not reflected in the documentation or release notes.

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

Docs all refer to legacy pools: 

.rgw
.rgw.control
.rgw.gc
.log
.intent-log
.usage
.users
.users.email
.users.swift
.users.uid

https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/object_gateway_guide_for_red_hat_enterprise_linux/#administrative-data-storage-rgw

Some of these pools no longer exist in 3.0 + as the pools have been consolidated to a "meta" pool.

"user_keys_pool": "us-east.rgw.meta:users.keys",
"user_email_pool": "us-east.rgw.meta:users.email",
"user_swift_pool": "us-east.rgw.meta:users.swift",
"user_uid_pool": "us-east.rgw.meta:users.uid",

http://docs.ceph.com/docs/luminous/radosgw/pools/

Comment 1 John Brier 2019-02-22 17:31:48 UTC

Thanks very much for the report Tupper!

We will take a look.

Comment 2 Giridhar Ramaraju 2019-08-05 13:08:41 UTC

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

Regards,
Giri

Comment 3 Giridhar Ramaraju 2019-08-05 13:10:06 UTC

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

Regards,
Giri

Comment 4 Giridhar Ramaraju 2019-08-20 07:17:12 UTC

Level setting the severity of this defect to "High" with a bulk update. Pls
refine it to a more closure value, as defined by the severity definition in
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity