Bug 1745565

Summary:	Remove the default arbiter check for vmstore volume
Product:	[oVirt] cockpit-ovirt	Reporter:	bipin <bshetty>
Component:	gluster-ansible	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bipin <bshetty>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.13.6	CC:	bugs, musoni, rcyriac, rhs-bugs, sabose, sasundar
Target Milestone:	ovirt-4.3.6	Keywords:	Regression, ZStream
Target Release:	0.13.8	Flags:	sasundar: ovirt-4.3? sasundar: blocker? sbonazzo: planning_ack? godas: devel_ack+ sasundar: testing_ack+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.13.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1745560	Environment:
Last Closed:	2019-09-26 19:42:49 UTC	Type:	---
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:	1745560, 1748891

Description bipin 2019-08-26 11:16:02 UTC

+++ This bug was initially created as a clone of Bug #1745560 +++

Description of problem:
=======================
The vmstore volume by default has the arbiter button checked. Would be ideal to revert back the change.


Version-Release number of selected component (if applicable):
=============================================================
ansible-2.8.4-1.el7ae.noarch
gluster-ansible-roles-1.0.5-4.el7rhgs.noarch


How reproducible:
================

Steps to Reproduce:
==================
1.
2.
3.

Actual results:
==============

Expected results:
================

Additional info:
===============

Comment 1 Mugdha Soni 2019-08-28 07:12:16 UTC

The same issue is seen single node deployment as well and the arbiter checkbox cannot be unchecked as checkbox is non editable.

Comment 2 bipin 2019-09-06 04:14:24 UTC

Tested with cockpit-ovirt-dashboard-0.13.8-1.el7ev.noarch.
The issue is not seen now. So moving the bug to verified.

Comment 3 Sandro Bonazzola 2019-09-26 19:42:49 UTC

This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.