Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1611956

Summary:	[HC] Deployment should set fencing policy to ensure HC environment works
Product:	[oVirt] cockpit-ovirt	Reporter:	Sahina Bose <sabose>
Component:	Gdeploy	Assignee:	Gobinda Das <godas>
Status:	CLOSED DUPLICATE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	0.11.3	CC:	bugs
Target Milestone:	ovirt-4.4.0	Flags:	rule-engine: ovirt-4.3+ sabose: devel_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1638221 (view as bug list)		Environment:
Last Closed:	2019-07-19 06:51:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1610782, 1638221, 1775552

Description Sahina Bose 2018-08-03 07:19:37 UTC

Description of 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:

Comment 3 Sandro Bonazzola 2019-01-28 09:43:59 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.

Comment 4 Sahina Bose 2019-07-19 06:51:22 UTC


*** This bug has been marked as a duplicate of bug 1638221 ***