Bug 1547012

Summary: Bricks getting assigned to different pids depending on whether brick path is IP or hostname based
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasad Desala <tdesala>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED ERRATA QA Contact: Bala Konda Reddy M <bmekala>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: rhinduja, rhs-bugs, sheggodu, storage-qa-internal, tdesala, vbellur
Target Milestone: ---   
Target Release: RHGS 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: brick-multiplexing
Fixed In Version: glusterfs-3.12.2-5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1547068 (view as bug list) Environment:
Last Closed: 2018-09-04 06:42:45 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: 1547068    
Bug Blocks: 1503137    

Description Prasad Desala 2018-02-20 10:48:55 UTC 
Description of problem:
=======================
Bricks getting assigned to different pids depending on whether brick path is IP or hostname based

Version-Release number of selected component (if applicable):
3.12.2-4.el7rhgs.x86_64

How reproducible:
always

Steps to Reproduce:
===================
1) Enable brick-mux.  
2) Create a volume with server hostnames as below,
gluster v create hostname replica 3 <hostname1:/brickpath> <hostname2:/brickpath> <hostname3:/brickpath> ...
3) Start the volume and make a note of glusterfsd pid
4) Now, create a new volume with server IP as below,
gluster v create IP replica 3 <IP1:/brickpath> <IP2:/brickpath> <IP3:/brickpath> ...
5) Start the volume and make a note of glusterfsd pid.

Actual results:
===============
For the two volumes, two different pids are getting assigned.

Expected results:
=================
As brick-mux is enabled, the two volumes should get the same brick process.
Comment 6 Atin Mukherjee 2018-02-20 13:18:49 UTC 
upstream patch : https://review.gluster.org/19601
Comment 11 Bala Konda Reddy M 2018-04-13 09:50:34 UTC 
Build : 3.12.2-7

Followed the steps mentioned in the description. 
Bricks are getting attached to the existing brick process irrespective of the volume created using hostname or ip.

Hence marking it as verified.
Comment 13 errata-xmlrpc 2018-09-04 06:42:45 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/RHSA-2018:2607