+++ This bug was initially created as a clone of Bug #882807 +++ Currently a host cannot be removed from a gluster cluster if it has any volume bricks on it, or is non-responsive. Introduce a "force" option while removing a host, so that such host can also be removed. This internally should send the "force" option to the "gluster peer detach" command. On the UI, this should be a checkbox on the "remove host" confirmation dialog This option should also be available in the REST api for removing a host. --- Additional comment from Dhandapani on 2012-12-11 04:52:04 EST --- Engine patch sent to upstream. http://gerrit.ovirt.org/#/c/8894/ UI patch needs to be send. --- Additional comment from Kanagaraj on 2012-12-18 01:50:25 EST --- UI patch sent to upstream: http://gerrit.ovirt.org/10180 --- Additional comment from Dhandapani on 2012-12-19 01:43:53 EST --- Another engine side fix required. If all the hosts are down in a given cluster the engine should remove the hosts entries in the db. --- Additional comment from Dhandapani on 2012-12-26 11:42:42 EST --- Engine patch sent to upstream: http://gerrit.ovirt.org/#/c/10401/
Documentation has been published on https://access.redhat.com/site/documentation/Red_Hat_Enterprise_Virtualization/ as part of the RHEV 3.2 GA.