Bug 1653575 - [RHHI-V] Support single brick distribute volume for RHHI-V volumes
Summary: [RHHI-V] Support single brick distribute volume for RHHI-V volumes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-ansible
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHGS 3.4.z Batch Update 4
Assignee: Sachidananda Urs
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1653576
TreeView+ depends on / blocked
 
Reported: 2018-11-27 07:30 UTC by SATHEESARAN
Modified: 2019-03-27 03:44 UTC (History)
7 users (show)

Fixed In Version: gluster-ansible-features-1.0.4-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1653576 (view as bug list)
Environment:
Last Closed: 2019-03-27 03:44:39 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0661 0 None None None 2019-03-27 03:44:53 UTC

Description SATHEESARAN 2018-11-27 07:30:54 UTC
Description of problem:
-----------------------
Currently the RHGS volumes created for RHHI-V are of replica 3 or arbitrated replica 3 volume only. RHHI-V also supports single brick volume. For this use case, gluster-ansible role should support creation of single brick volume ( distribute volume with single brick )

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHHI-V 1.5.z
gluster-ansible-roles-1.0.4

How reproducible:
-----------------
Not applicable

Steps to Reproduce:
-------------------
1. Try to create single brick distribute RHGS volume by having single host entry

Actual results:
---------------
No way to create single brick distribute volume

Expected results:
-----------------
gluster-ansible role should support single brick distribute volume

Comment 2 SATHEESARAN 2018-11-28 11:09:51 UTC
Make sure that the granular-entry-heal option is not turned on for the distribute volume. As this option is not relevant for the distribute volume.

Does this item needs a separate bug to be tracked ?

Comment 3 Sachidananda Urs 2018-11-29 05:01:33 UTC
(In reply to SATHEESARAN from comment #2)
> Make sure that the granular-entry-heal option is not turned on for the
> distribute volume. As this option is not relevant for the distribute volume.
> 
> Does this item needs a separate bug to be tracked ?

No need, this bug is good enough. Thanks sas.

Comment 4 Sahina Bose 2018-12-18 07:18:04 UTC
Can this be targeted to 3.4 U3 or U4?

Comment 5 Sachidananda Urs 2018-12-20 06:45:38 UTC
(In reply to Sahina Bose from comment #4)
> Can this be targeted to 3.4 U3 or U4?

We can do this for U4.

Comment 6 Sachidananda Urs 2018-12-26 06:02:37 UTC
Commit: https://github.com/gluster/gluster-ansible-features/commit/99b688dcdd50 fixes the issue.

Comment 7 SATHEESARAN 2019-01-09 06:41:02 UTC
Additional information here is that the new virt profile for distributed volume is now available with the name 'distributed-virt'
The following way used to optimize the distribute volume for virt store usecase:
# gluster volume set <vol> group distributed-virt

Comment 8 Sachidananda Urs 2019-01-10 04:58:36 UTC
(In reply to SATHEESARAN from comment #7)
> Additional information here is that the new virt profile for distributed
> volume is now available with the name 'distributed-virt'
> The following way used to optimize the distribute volume for virt store
> usecase:
> # gluster volume set <vol> group distributed-virt

sas, will this group be part of U4?

Comment 9 Sachidananda Urs 2019-01-10 05:44:44 UTC
(In reply to Sachidananda Urs from comment #8)
> (In reply to SATHEESARAN from comment #7)
> > Additional information here is that the new virt profile for distributed
> > volume is now available with the name 'distributed-virt'
> > The following way used to optimize the distribute volume for virt store
> > usecase:
> > # gluster volume set <vol> group distributed-virt
> 
> sas, will this group be part of U4?

If so, this can be set from the role by setting the: gluster_features_hci_volume_options variable.

Comment 13 Sahina Bose 2019-02-07 13:03:02 UTC
(In reply to Sachin P Mali from comment #12)
> In release stakeholders meeting  it was agreed to push this bug out of
> proposed list of 3.4 BU4, and to be considered for a future batch update.

This bug is needed for RHHI 1.6 as we move the deployment flow to be based on gluster-ansibles. Can this decision be re-evaluated as the verification of bug will be done by RHHI QE?

Comment 19 SATHEESARAN 2019-02-23 17:34:36 UTC
Tested with gluster-ansible-features-1.0.4-3

distributed volume is created as part of single node deployment and required volume options are set on it

Comment 21 errata-xmlrpc 2019-03-27 03:44:39 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:0661


Note You need to log in before you can comment on or make changes to this bug.