[Bugs] [Bug 1464072] cns-brick-multiplexing: brick process fails to restart after gluster pod failure

[bugzilla at redhat.com]

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



--- Comment #4 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17601 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit b71059960f8c67d9a058244d2a1c748be4fe1323
Author: Mohit Agrawal <moagrawa at redhat.com>
Date:   Thu Jun 22 16:57:04 2017 +0530

    glusterd: brick process fails to restart after gluster pod failure

    Problem: In container environment sometime after delete gluster pod
             and created new gluster pod brick process doesn't seem
             to come up.

    Solution: On the basis of logs it seems glusterd is trying to attach
              with non glusterfs process.Change the code of function
              glusterd_get_sock_from_brick_pid to fetch socketpath from
argument
              of running brick process.

    BUG: 1464072
    Change-Id: Ida6af00066341b683bbb4440d7a0d8042581656a
    Signed-off-by: Mohit Agrawal <moagrawa at redhat.com>
    Reviewed-on: https://review.gluster.org/17601
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=XTJEKobOJ4&a=cc_unsubscribe