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 1533413

Summary:	[Doc 2.x ] - Admin Guide - ceph-ansible way of shrinking cluster needs to be added
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vasishta <vashastr>
Component:	Documentation	Assignee:	Bara Ancincova <bancinco>
Status:	CLOSED WONTFIX	QA Contact:	Vasishta <vashastr>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.5	CC:	asriram, hnallurv, kdreyer, vashastr
Target Milestone:	rc
Target Release:	2.5
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:	2018-01-22 08:13:09 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:	1532294

Description Vasishta 2018-01-11 09:56:04 UTC

Description of problem:
ceph-ansible way of shrinking cluster needs to be added to 2.x guide with minor addition from the 3.x admin guide (6.2.1 and 6.4.1)

Version-Release number of selected component (if applicable):
2.x guide

How reproducible:
always

Issue with following steps existing 3.x guide to shrink OSD (6.4.1) -
If OSD node doesn't contain admin keyring -

Actual results:
"msg": "The Ceph admin key is not present on the OSD node, please add it and remove it after the playbook is done."

Expected results:
OSD must be removed without any failure

A new step can be added either before existing step 1 or as a prerequisite explaining procedure to copy admin keyring from mon. A note can be added asking user to remove keyring once OSD is removed if not needed.

Comment 4 Harish NV Rao 2018-01-11 10:10:32 UTC

@Vasishta, this applies only from 2.5 onward. Right? If yes, doc team needs to add a note for the same.

Comment 5 Vasishta 2018-01-11 10:32:31 UTC

Hi Harish,

Yes, This applies only from RHCEPH 2.5 (with ceph-ansible-3.0.16* onwards)

Doc team, Can you please add a note saying that this feature is for RHCEPH 2.5 onwards ?

Regards,
Vasishta

Comment 6 Vasishta 2018-01-22 08:12:04 UTC

Hi Bara,

Product has clarified that this 3.0 feature will not be available for 2.x though it is the new ceph-ansible we have.

Can you please close this BZ as WON'T FIX ?

Regards,
Vasishta