Bug 1129095

Summary: vol heal info returning a hostname that does not match peer/brick node names in multi-homed pool
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Paul Cuzner <pcuzner>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED CURRENTRELEASE QA Contact: storage-qa-internal <storage-qa-internal>
Severity: low Docs Contact:
Priority: low    
Version: rhgs-3.0CC: ravishankar, rhs-bugs, storage-qa-internal, vagarwal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-09 15:46:52 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:
Attachments:
Description Flags
example showing the mismatch between peer/brick names and vol heal info none

Description Paul Cuzner 2014-08-12 08:49:19 UTC
Created attachment 925971 [details]
example showing the mismatch between peer/brick names and vol heal info

Description of problem:
I have a trusted pool that has a front end network for nfs and a backend network for gluster. The front end network uses the servers hostname for client connectivity and the gluster network uses a different subnet and node names for the trusted pool.

vol info in this environment returns a brick name that references the name of the hosts on the client side network not the gluster network.




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

How reproducible:
this behavior is always seen

Steps to Reproduce:
1. create a cluster as shown above
2. run the commands (example output attached)
3.

Actual results:
vol heal provides bricknames using the incorrect node names


Expected results:
vol heal info brick information should match the brick paths known by gluster and shown in the other commands like vol status/vol info.

Additional info:

Comment 2 Ravishankar N 2015-12-09 15:46:52 UTC
This was fixed upstream in BZ 1265633 and is also available in RHGS 3.1.1 as part of rebase. Hence closing this bug. Feel free to re-open if I have overlooked something,