[Bugs] [Bug 1316391] New: Brick ports get changed after GlusterD restart

[bugzilla at redhat.com]

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

            Bug ID: 1316391
           Summary: Brick ports get changed after GlusterD restart
           Product: GlusterFS
           Version: 3.7.9
         Component: glusterd
          Assignee: kaushal at redhat.com
          Reporter: kaushal at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org
        Depends On: 1313628
            Blocks: 1306656



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

The following sequence of steps can lead to the brick ports changing, which can
break firewall rules and lead to a brick being inaccessible from the client.

1. Stop the volume
2. Stop glusterd on one node.
3a. Start the volume from some other node, or
3b. do a volume set operation
4. Start glusterd on the downed node again.
5. If 3b was done, start volume now.
Result: Brick ports on the downed node change

--- Additional comment from Vijay Bellur on 2016-03-02 16:22:33 IST ---

REVIEW: http://review.gluster.org/13578 (glusterd: Always copy old brick ports
when importing) posted (#1) for review on master by Kaushal M
(kaushal at redhat.com)

--- Additional comment from Vijay Bellur on 2016-03-07 13:06:34 IST ---

REVIEW: http://review.gluster.org/13578 (glusterd: Always copy old brick ports
when importing) posted (#2) for review on master by Kaushal M
(kaushal at redhat.com)

--- Additional comment from Vijay Bellur on 2016-03-10 12:52:11 IST ---

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>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1306656
[Bug 1306656] [GSS] - Brick ports changed after configuring I/O and
management encryption
https://bugzilla.redhat.com/show_bug.cgi?id=1313628
[Bug 1313628] Brick ports get changed after GlusterD restart
-- 
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=0EgKXuev3M&a=cc_unsubscribe