Bug 1434774 - Order of host names should be preserved while creating volumes
Summary: Order of host names should be preserved while creating volumes
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
Target Milestone: ---
: RHGS 3.3.0
Assignee: Sachidananda Urs
Depends On:
Blocks: Gluster-HC-3 1417151 RHHI-1.1-Approved-Backlog-BZs
TreeView+ depends on / blocked
Reported: 2017-03-22 11:02 UTC by SATHEESARAN
Modified: 2017-09-21 04:49 UTC (History)
5 users (show)

Fixed In Version: gdeploy-2.0.2-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-09-21 04:49:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2777 normal SHIPPED_LIVE gdeploy bug fix and enhancement update for RHEL7 2017-09-21 08:23:08 UTC

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):

How reproducible:

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.


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