[Bugs] [Bug 1478710] New: when gluster pod is restarted, bricks from the restarted pod fails to connect to fuse, self-heal etc

[bugzilla at redhat.com]

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

            Bug ID: 1478710
           Summary: when gluster pod is restarted, bricks from the
                    restarted pod fails to connect to fuse, self-heal etc
           Product: GlusterFS
           Version: mainline
         Component: protocol
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: moagrawa at redhat.com
                CC: akhakhar at redhat.com, amukherj at redhat.com,
                    annair at redhat.com, bugs at gluster.org,
                    hchiramm at redhat.com, jrivera at redhat.com,
                    kramdoss at redhat.com, madam at redhat.com,
                    mliyazud at redhat.com, mzywusko at redhat.com,
                    pprakash at redhat.com, rcyriac at redhat.com,
                    rhs-bugs at redhat.com, rkavunga at redhat.com,
                    rreddy at redhat.com, rtalur at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1477024
            Blocks: 1417151, 1475340, 1477020




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1475340
[Bug 1475340] [Tracker Bug (RHGS)] Glusterfs mount inside POD gets
terminated when scaled with brick multiplexing enabled
https://bugzilla.redhat.com/show_bug.cgi?id=1477020
[Bug 1477020] [Tracker Bug (RHGS)] when gluster pod is restarted, bricks
from the restarted pod fails to connect to fuse, self-heal etc
https://bugzilla.redhat.com/show_bug.cgi?id=1477024
[Bug 1477024] when gluster pod is restarted, bricks from the restarted pod
fails to connect to fuse, self-heal etc
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.