[Bugs] [Bug 1368055] [geo-rep] Stopped geo-rep session gets started automatically once all the master nodes are upgraded

[bugzilla at redhat.com]

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



--- Comment #3 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/15197 committed in release-3.7 by Aravinda VK
(avishwan at redhat.com) 
------
commit 26c153bec24c0c0a37e788707f6ca793890279f0
Author: Saravanakumar Arumugam <sarumuga at redhat.com>
Date:   Wed Jun 29 15:36:06 2016 +0530

    glusterd/geo-rep: Handle empty monitor.status during upgrade

    Problem:
    Consider geo-replication is in Stopped state.
    Following which, glusterfs is upgraded (where monitor.status is the new
status file).

    Now, When geo-replication status command is run,
    empty monitor status file gets created.

    Now, if glusterd is restarted, it reads empty monitor status
    and  starts geo-replication session. This is incorrect as session
    was in Stopped state earlier.

    Solution:
    If monitor status is empty, error out and avoid
    starting geo-replication session.

    Note: if monitor status is empty, geo-rep session is displayed
    as Stopped state.

    Change-Id: Ifb3db896e5ed92b927764cf1163503765cb08bb4
    BUG: 1368055
    Signed-off-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    > Reviewed-on: http://review.gluster.org/14830
    > 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: Jeff Darcy <jdarcy at redhat.com>
    (cherry picked from commit f938b3a26ffab9482d5f910ee76d2bb2b370517f)
    Reviewed-on: http://review.gluster.org/15197
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.