Bug 1415762

Summary:	[RFE] heketi-cli should support replacement of a failed devices
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Mohamed Ashiq <mliyazud>
Component:	heketi	Assignee:	Raghavendra Talur <rtalur>
Status:	CLOSED ERRATA	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	cns-3.5	CC:	bmohanra, hchiramm, mliyazud, pprakash, rcyriac, rhs-bugs, rtalur, storage-qa-internal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	CNS 3.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	heketi-4.0.0-2.el7rhgs	Doc Type:	Enhancement
Doc Text:	Device Remove is a feature that allows heketi to move bricks from a failed device to other devices. This way administrators can perform operations on the failed device without losing brick data. As the copy of data happens with the replace brick of gluster, which internally triggers selfheal, bricks can be moved to a safer device and volumes will be served without any down time.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-20 18:37:32 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:	1435613
Bug Blocks:	1415595

Description Mohamed Ashiq 2017-01-23 16:41:45 UTC

Description of problem:

heketi-cli currently supports only add and delete of a device. It should also support a cleaner way to replace a failed device as well:

#####
# heketi-cli device -h
Heketi Device Management

Usage:
  heketi-cli device [command]

Available Commands:
  add         Add new device to node to be managed by Heketi
  delete      Deletes a device from Heketi node
  disable     Disallow usage of a device by placing it offline
  enable      Allows device to go online
  info        Retreives information about the device

#####

Comment 8 Bhavana 2017-04-18 09:06:39 UTC

Hi Ashiq,

I have edited the doc text for the errata. Please review the same and share your comments if any.

Comment 10 errata-xmlrpc 2017-04-20 18:37:32 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/RHEA-2017:1111