Bug 1273868

Summary:	Heketi doesn't allow deleting nodes with drives missing/inaccessible
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Anush Shetty <ashetty>
Component:	heketi	Assignee:	Luis Pabón <lpabon>
Status:	CLOSED ERRATA	QA Contact:	Anush Shetty <ashetty>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	asrivast, madam, sankarshan
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	heketi-1.0.1-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-01 05:44:11 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:	1260783

Description Anush Shetty 2015-10-21 12:21:02 UTC

Description of problem: When drives are unreachable/missing from a node where volumes existed, heketi has no provision to delete the node from the cluster. Hence even the cluster it belongs to cannot be deleted without removing the db file. Volumes associated with the node can be deleted though. 


Version-Release number of selected component (if applicable): 1.0.0 (Upstream build)


How reproducible: Always


Steps to Reproduce:
1. Create a cluster and then create a heketi volume
2. On one of the nodes, disable the drives (shutdown the machine)
3. Try deleting the node

Actual results:

Node deletion fails.

Comment 2 Luis Pabón 2015-10-21 14:38:23 UTC

Github Issue: https://github.com/heketi/heketi/issues/232

Comment 5 Anush Shetty 2015-11-24 11:57:42 UTC

Heketi deletes the entry from its database. On the node, an application will have to go and cleanup the volume groups/bricks manually.

Verified with heketi-1.0.1-1.el7rhgs.x86_64

Comment 7 errata-xmlrpc 2016-03-01 05:44:11 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://rhn.redhat.com/errata/RHBA-2016-0193.html