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.
Github Issue: https://github.com/heketi/heketi/issues/232
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
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