Bug 1745560 - Remove the default arbiter check for vmstore volume
Summary: Remove the default arbiter check for vmstore volume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.6.z Async Update
Assignee: Sahina Bose
QA Contact: bipin
URL:
Whiteboard:
Depends On: 1745565
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-26 11:12 UTC by bipin
Modified: 2019-10-03 12:24 UTC (History)
3 users (show)

Fixed In Version: cockpit-ovirt-dashboard-0.13.8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1745565 (view as bug list)
Environment:
Last Closed: 2019-10-03 12:24:01 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2963 0 None None None 2019-10-03 12:24:08 UTC

Description bipin 2019-08-26 11:12:08 UTC 
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 SATHEESARAN 2019-09-06 05:05:49 UTC 
The fix is already available in the build - cockpit-ovirt-dashboard-0.13.8
And also the dependent oVirt bug is ON_QA
Comment 2 bipin 2019-09-06 05:14:29 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 4 errata-xmlrpc 2019-10-03 12:24:01 UTC 
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.

https://access.redhat.com/errata/RHBA-2019:2963
Note You need to log in before you can comment on or make changes to this bug.