[Bugs] [Bug 1743219] New: glusterd start is failed and throwing an error Address already in use

[bugzilla at redhat.com]

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

            Bug ID: 1743219
           Summary: glusterd start is failed and throwing an error Address
                    already in use
           Product: GlusterFS
           Version: 6
            Status: NEW
         Component: rpc
          Assignee: bugs at gluster.org
          Reporter: moagrawa at redhat.com
                CC: bugs at gluster.org
        Depends On: 1743020
            Blocks: 1743218
  Target Milestone: ---
    Classification: Community



+++ This bug was initially created as a clone of Bug #1743020 +++

Description of problem:
Some of the .t are failing due to glusterd start failed after kill all gluster
processes.

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


How reproducible:
Run regression test suite and below test case are failing
./tests/bugs/glusterd/brick-mux-validation.t
./tests/bugs/cli/bug-1077682.t
./tests/basic/glusterd-restart-shd-mux.t
./tests/bugs/core/multiplex-limit-issue-151.t

Steps to Reproduce:
1.
2.
3.

Actual results:
test cases are failing

Expected results:
test case should not fail

Additional info:

--- Additional comment from Worker Ant on 2019-08-18 15:59:49 UTC ---

REVIEW: https://review.gluster.org/23211 (rpc: glusterd start is failed and
throwing an error Address already in use) posted (#9) for review on master by
MOHIT AGRAWAL

--- Additional comment from Worker Ant on 2019-08-19 03:45:41 UTC ---

REVIEW: https://review.gluster.org/23211 (rpc: glusterd start is failed and
throwing an error Address already in use) merged (#9) on master by MOHIT
AGRAWAL


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1743020
[Bug 1743020] glusterd start is failed and throwing an error Address already in
use
https://bugzilla.redhat.com/show_bug.cgi?id=1743218
[Bug 1743218] glusterd start is failed and throwing an error Address already in
use
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.