Bug 1368053

Summary:	[geo-rep] Stopped geo-rep session gets started automatically once all the master nodes are upgraded
Product:	[Community] GlusterFS	Reporter:	Saravanakumar <sarumuga>
Component:	geo-replication	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.8.0	CC:	amukherj, avishwan, bugs, csaba, rhinduja, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1351071	Environment:
Last Closed:	2016-08-24 10:21:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1347625, 1351071, 1368055
Bug Blocks:

Comment 1 Vijay Bellur 2016-08-18 08:47:37 UTC

REVIEW: http://review.gluster.org/15196 (glusterd/geo-rep: Handle empty monitor.status during upgrade) posted (#1) for review on release-3.8 by Saravanakumar Arumugam (sarumuga)

Comment 2 Vijay Bellur 2016-08-19 06:33:58 UTC

REVIEW: http://review.gluster.org/15196 (glusterd/geo-rep: Handle empty monitor.status during upgrade) posted (#2) for review on release-3.8 by Saravanakumar Arumugam (sarumuga)

Comment 3 Vijay Bellur 2016-08-19 10:46:55 UTC

COMMIT: http://review.gluster.org/15196 committed in release-3.8 by Aravinda VK (avishwan) 
------
commit 10d044b62e476e032e8bda59fe8fbb3b8b0576b4
Author: Saravanakumar Arumugam <sarumuga>
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: 1368053
    Signed-off-by: Saravanakumar Arumugam <sarumuga>
    > Reviewed-on: http://review.gluster.org/14830
    > Smoke: Gluster Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Reviewed-by: Jeff Darcy <jdarcy>
    (cherry picked from commit f938b3a26ffab9482d5f910ee76d2bb2b370517f)
    Reviewed-on: http://review.gluster.org/15196
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Aravinda VK <avishwan>

Comment 4 Niels de Vos 2016-08-24 10:21:38 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.3, please open a new bug report.

glusterfs-3.8.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://www.gluster.org/pipermail/announce/2016-August/000059.html
[2] https://www.gluster.org/pipermail/gluster-users/