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.
upstream patch : https://review.gluster.org/19601
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.
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