[Bugs] [Bug 1421590] New: Bricks take up new ports upon volume restart after add-brick op with brick mux enabled

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1421590

            Bug ID: 1421590
           Summary: Bricks take up new ports upon volume restart after
                    add-brick op with brick mux enabled
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: sbairagy at redhat.com
                CC: bugs at gluster.org



Description of problem:


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


How reproducible:


Steps to Reproduce and actual results:

Taking a 1 node cluster here to list down the steps to reproduce, but this can
be reproduced on multi-node cluster too.

1. Enable brick multiplexing
2. Create 1 volume with one brick
2. Start the volume and check volume status. The brick will be using port 49152
3. Add a brick to the volume and check vol status. Both bricks use 49152
4. Stop the volume and then start it.
5. Check volume status. Both bricks now use 49153.
6. If you restart the volume again and check the status, the bricks would now
use 49154. For every restart, the bricks take up the next port.

Expected results:
The bricks should use the ports being used upon restart and not take up a new
port.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.