Bug 1434774

Summary:	Order of host names should be preserved while creating volumes
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	gdeploy	Assignee:	Sachidananda Urs <surs>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	amukherj, rhinduja, rhs-bugs, smohan, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.3.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gdeploy-2.0.2-2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-21 04:49:50 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:
Bug Blocks:	1411323, 1417151, 1485863

Description SATHEESARAN 2017-03-22 11:02:05 UTC

Description of problem:
-----------------------
The hosts listed under [hosts] section are not preserved while creating the volumes. This really becomes the issue, that placement of arbiter brick can't be determined

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gdeploy-2.0.1.el7rhgs

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Inside the hosts section provide the IPs in any order.

Actual results:
---------------
Volumes are created with brick chosen from host with hostnames lexicographical arranged.

Expected results:
-----------------
The order of hosts listed in [hosts] section should be preserved

Comment 2 Sachidananda Urs 2017-03-30 06:13:16 UTC

Commit: https://github.com/gluster/gdeploy/commit/2f71d033a270 should fix the issue.

Comment 5 SATHEESARAN 2017-04-24 09:40:11 UTC

Tested with gdeploy-2.0.2-3.el7rhgs.

Verified that the order of the hostnames are preserved while picking bricks from those hosts.

Comment 7 errata-xmlrpc 2017-09-21 04:49:50 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-2017:2777