Bug 1774851

Summary:	Adding support to create gluster volumes for specific nodes from ansible roles
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Gobinda Das <godas>
Component:	rhhi	Assignee:	Gobinda Das <godas>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	bkunal, jcrumple, mduasope, mkalinin, myllynen, nravinas, rcyriac, rhs-bugs, sabose, sasundar, seamurph
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHHI-V 1.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Previously, volumes were created across all nodes. In deployments larger than three nodes, you can now select which nodes you want volumes to be deployed across.	Story Points:	---
Clone Of:
Clones:	1774852 1788914 (view as bug list)		Environment:
Last Closed:	2020-02-13 15:57:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1774852
Bug Blocks:	1788914

Description Gobinda Das 2019-11-21 06:09:25 UTC

Description of problem:
 Now gluster ansible roles only support to create gluster volumes across all nodes, but incase of 6 nodes usecase if user wants to create some volume in 3 nodes and other volumes in other nodes then it's not possible now.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
 Should have way to create volume for specific nodes


Additional info:

Comment 2 Sahina Bose 2019-11-22 08:52:01 UTC

*** Bug 1775537 has been marked as a duplicate of this bug. ***

Comment 22 SATHEESARAN 2019-12-30 12:17:31 UTC

Tested with gluster-ansible-roles-1.0.5-7 and gluster-ansible-features-1.0.5-5 with following steps.

node{1..6} were used.

Bricks for engine volume are created on node{1,2,3}
Bricks for vmstore & data are created on node{4,5,6|


[root@ ~]# gluster volume info | grep -i brick
Number of Bricks: 1 x 3 = 3
Bricks:
Brick1: node10.test.com:/gluster_bricks/data/data
Brick2: node11.test.com:/gluster_bricks/data/data
Brick3: node12.test.com:/gluster_bricks/data/data
Number of Bricks: 1 x 3 = 3
Bricks:
Brick1: node7.test.com:/gluster_bricks/engine/engine
Brick2: node8.test.com:/gluster_bricks/engine/engine
Brick3: node9.test.com:/gluster_bricks/engine/engine
Number of Bricks: 1 x (2 + 1) = 3
Bricks:
Brick1: node10.test.com:/gluster_bricks/vmstore/vmstore
Brick2: node11.test.com:/gluster_bricks/vmstore/vmstore
Brick3: node12.test.com:/gluster_bricks/vmstore/vmstore (arbiter)

Comment 35 Sean Murphy 2020-01-16 22:50:02 UTC

Miguel - as you've seen by now I was overly optimistic about the 1.7 timing relative to Airbus' roll-out rhythm, and I and other now have approved the 1.6 + fix Support Exception.

Note the proviso statement in the SE - we need to work and be planful about getting 1.7 / 1.8 into the Airbus roll-out at the earliest possible juncture.

sean

Comment 52 errata-xmlrpc 2020-02-13 15:57:23 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-2020:0508