Bug 1228843

Summary:	[RFE] introduce and document single-command procedure to pull drive from cluster
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Federico Lucifredi <flucifre>
Component:	RADOS	Assignee:	Josh Durgin <jdurgin>
Status:	CLOSED DUPLICATE	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.3.0	CC:	ceph-eng-bugs, dzafman, flucifre, hnallurv, kchai, kdreyer, nlevine, sjust, uboppana, yweinste
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-18 20:25:49 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 Federico Lucifredi 2015-06-05 21:32:31 UTC

Description of problem:

Customer would like a command/script to manually remove a disk, and include in official documentation a manual procedure to set individual disk to zero-weight and pull. It is understood there is a way to do this already, what is desired is simple UX via a single command.

Too much understanding needed on part of user to pull a disk out of the cluster. this should be "something a person paid $7 an hour can do", without knowing what's happening underneath says $CUSTOMER.

Comment 4 Federico Lucifredi 2015-06-05 21:40:27 UTC

upstream bug: http://tracker.ceph.com/issues/11900

Comment 8 Ken Dreyer (Red Hat) 2015-07-15 22:53:27 UTC

I'm not sure what to make of Sam's response to the upstream bug there, it's a little light on details :)

Comment 9 Samuel Just 2015-07-15 22:58:02 UTC

Sorry, just a quick list of the things that need to be handled.  This has not been done yet.

Comment 11 Neil Levine 2016-02-05 19:22:06 UTC

F2: can we assign as a USM task rather than a RADOS one?

Comment 18 Josh Durgin 2017-07-18 20:25:49 UTC


*** This bug has been marked as a duplicate of bug 1464945 ***