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.
Engine patch sent to upstream. http://gerrit.ovirt.org/#/c/8894/ UI patch needs to be send.
UI patch sent to upstream: http://gerrit.ovirt.org/10180
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.
Engine patch sent to upstream: http://gerrit.ovirt.org/#/c/10401/
Verified
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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. http://rhn.redhat.com/errata/RHSA-2013-0888.html