[Bugs] [Bug 1322145] Glusterd fails to restart after replacing a failed GlusterFS node and a volume has a snapshot

[bugzilla at redhat.com]

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



--- Comment #33 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16907 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 1c92f83ec041176ad7c42ef83525cda7d3eda3c5
Author: Gaurav Yadav <gyadav at redhat.com>
Date:   Thu Mar 16 14:56:39 2017 +0530

    glusterd : Disallow peer detach if snapshot bricks exist on it

    Problem :
    - Deploy gluster on 2 nodes, one brick each, one volume replicated
    - Create a snapshot
    - Lose one server
    - Add a replacement peer and new brick with a new IP address
    - replace-brick the missing brick onto the new server
      (wait for replication to finish)
    - peer detach the old server
    - after doing above steps, glusterd fails to restart.

    Solution:
      With the fix detach peer will populate an error : "N2 is part of
      existing snapshots. Remove those snapshots before proceeding".
      While doing so we force user to stay with that peer or to delete
      all snapshots.

    Change-Id: I3699afb9b2a5f915768b77f885e783bd9b51818c
    BUG: 1322145
    Signed-off-by: Gaurav Yadav <gyadav at redhat.com>
    Reviewed-on: https://review.gluster.org/16907
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

-- 
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=i7UmvQoWh3&a=cc_unsubscribe