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 1464973

Summary:	[RFE]: Configuration option metadata
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	John Spray <john.spray>
Component:	RADOS	Assignee:	Josh Durgin <jdurgin>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.0	CC:	anharris, bniver, ceph-eng-bugs, dzafman, hnallurv, jdurgin, kchai, kdreyer, shmohan
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.0-1.el7cp Ubuntu: ceph_12.2.0-2redhat1xenial	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-05 23:34:34 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 John Spray 2017-06-26 10:34:49 UTC

A new structure for configuration options, including for each:
 * Categorise into basic/advanced/development
 * Doc string for non-development options
 * Label options with area of interest (performance, logging, etc)

Comment 3 Josh Durgin 2017-07-19 00:14:56 UTC

https://github.com/ceph/ceph/pull/16211

Comment 12 John Spray 2017-11-07 11:36:38 UTC

Here's a doc update for config set: https://github.com/ceph/ceph/pull/18789

It looks like you were doing "ceph config set" rather than "ceph tell <osd|mon|mds>.<id> config set".  The former will just set a config setting on whichever mon is the leader, rather than the daemon you wanted to update.

Also, the tags are there, it's just that most settings currently don't have any tags.

Comment 18 errata-xmlrpc 2017-12-05 23:34:34 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-2017:3387