Description of the problem: The gluster-HE deployment flow should set the following on the default cluster so that fencing does not result in quorum loss skip_fencing_if_gluster_bricks_up skip_fencing_if_gluster_quorum_not_met This needs to be added to the ansible playbook that's triggered post HE deployment. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: NA Actual results: Expected results: Additional info: --- Additional comment from SATHEESARAN on 2018-08-21 08:22:15 EDT --- Removing the customer case attached to the upstream bug --- Additional comment from Gobinda Das on 2018-08-21 08:29:46 EDT --- Moving this to 4.2.7 as the options are not supported in ansible module now. skip_fencing_if_gluster_bricks_up skip_fencing_if_gluster_quorum_not_met We need have to change ovirt ansible module to support both options.Which will take time to review and merge. --- Additional comment from Sahina Bose on 2018-11-21 10:28:22 UTC --- Gobinda, can you create an issue for adding the fencing support functionality in ovirt ansible module? --- Additional comment from Gobinda Das on 2018-11-28 05:36:27 UTC --- Issues created https://github.com/oVirt/ovirt-ansible/issues/163 --- Additional comment from Sandro Bonazzola on 2019-01-28 09:41:42 UTC --- This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. --- Additional comment from Gobinda Das on 2019-02-01 06:43:40 UTC --- @Simone/Ido Is there any way to add fencing support in ansible module? --- Additional comment from Sahina Bose on 2019-07-19 06:51:22 UTC ---
Tested with RHV Version 4.4.0-0.33.master.el8ev With the cluster that has both gluster and virt services enabled, the following fencing policies are enabled skip_fencing_if_gluster_bricks_up skip_fencing_if_gluster_quorum_not_met
Created attachment 1686001 [details] Verified screenshot
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 (RHHI for Virtualization 1.8 bug fix and enhancement update), 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-2020:3314