Bug 1569912

Summary: [RFE] check for duplicate hostnames through colonizer deployment
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nag Pavan Chilakam <nchilaka>
Component: gluster-colonizerAssignee: Dustin Black <dblack>
Status: CLOSED DEFERRED QA Contact: Rahul Hinduja <rhinduja>
Severity: medium Docs Contact:
Priority: medium    
Version: rhgs-3.4CC: dblack, nchilaka, rhs-bugs, rreddy, sankarshan
Target Milestone: ---Keywords: FutureFeature, Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-18 09:54:42 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:

Description Nag Pavan Chilakam 2018-04-20 09:00:28 UTC
Description of problem:
---------------------
currently we are not checking for duplicate hostnames when deploying through colonizer.
we check if the host IPs are duplicates but not the hostnames.
Hence the deployment proceeds with duplicate hostnames and fails during volume creation as bricks from different nodes have same brick path as hostnames are same, this leading to an inconsistent environment



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


Steps to Reproduce:
1.deploy colonizer 
2. choose hostname and IP selection as manual
3. enter same hostname for 2 nodes

Actual results:
--------------
duplicate hostnames are taken and deployment fails during vol creation as bricks paths are duplicate

Comment 4 Dustin Black 2018-04-25 22:13:18 UTC
Ack. We need to add duplicates checking to the hostnames input for manual node information entry.

Comment 7 Ramakrishna Reddy Yekulla 2018-11-19 08:58:48 UTC
This is a feature request for the colonizer tool. This feature request is  filed as an issue upstream at https://github.com/gluster/gluster-colonizer/issues/66

Comment 8 Yaniv Kaul 2019-04-18 09:54:42 UTC
Closing all Colonizer BZs (as DEFERRED) as we do not intend to work on them for the time being.