[Bugs] [Bug 1313628] Brick ports get changed after GlusterD restart

[bugzilla at redhat.com]

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



--- Comment #3 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13578 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit ecf6243bc435a00f3dd2495524cd6e48e2d56f72
Author: Kaushal M <kaushal at redhat.com>
Date:   Wed Mar 2 15:19:30 2016 +0530

    glusterd: Always copy old brick ports when importing

    When an updated volinfo is imported in, the brick ports from the old
    volinfo should be always copied.

    Earlier, this was being done only if the old volinfo was stopped and
    new volinfo was started. This could lead to brick ports chaging when the
    following sequence of steps happened.
    - A volume is stopped
    - GlusterD is stopped on a peer
    - The stopped volume is started
    - The stopped GlusterD is started
    This sequence would lead to bricks on the peer with re-started GlusterD
    to get new ports, which could break firewall rules and could prevent
    client access. This sequence could be hit when enabling management
    encryption in a Gluster trusted storage pool.

    Change-Id: I808ad478038d12ed2b19752511bdd7aa6f663bfc
    BUG: 1313628
    Signed-off-by: Kaushal M <kaushal at redhat.com>
    Reviewed-on: http://review.gluster.org/13578
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur at redhat.com>
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: Atin Mukherjee <amukherj at redhat.com>
    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=Qemik9sdf0&a=cc_unsubscribe