Bug 1342261

Summary:	[georep]: Stopping volume fails if it has geo-rep session (Even in stopped state)
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Rahul Hinduja <rhinduja>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED ERRATA	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	avishwan, csaba, rcyriac
Target Milestone:	---	Keywords:	Regression, ZStream
Target Release:	RHGS 3.1.3
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.9-8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1342420 (view as bug list)		Environment:
Last Closed:	2016-06-23 05:25:43 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:
Bug Blocks:	1311817, 1342420, 1342431, 1342634

Description Rahul Hinduja 2016-06-02 19:28:53 UTC

Description of problem:
=======================

Pre-requisite of stopping volume is to stop geo-rep session. Even if geo-rep session is stopped, it fails complaining that the geo-rep session is ACTIVE.

[root@dhcp37-88 scripts]# gluster volume stop MASTER
Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y
volume stop: MASTER: failed: geo-replication sessions are active for the volume MASTER.
Stop geo-replication sessions involved in this volume. Use 'volume geo-replication status' command for more info.
[root@dhcp37-88 scripts]# gluster volume geo-replication status
 
MASTER NODE     MASTER VOL    MASTER BRICK      SLAVE USER    SLAVE                       SLAVE NODE    STATUS     CRAWL STATUS    LAST_SYNCED          
---------------------------------------------------------------------------------------------------------------------------------------------
10.70.37.88     MASTER        /rhs/brick1/b1    root          ssh://10.70.37.52::SLAVE    N/A           Stopped    N/A             N/A                  
10.70.37.88     MASTER        /rhs/brick2/b4    root          ssh://10.70.37.52::SLAVE    N/A           Stopped    N/A             N/A                  
10.70.37.213    MASTER        /rhs/brick1/b3    root          ssh://10.70.37.52::SLAVE    N/A           Stopped    N/A             N/A                  
10.70.37.213    MASTER        /rhs/brick2/b6    root          ssh://10.70.37.52::SLAVE    N/A           Stopped    N/A             N/A                  
10.70.37.43     MASTER        /rhs/brick1/b2    root          ssh://10.70.37.52::SLAVE    N/A           Stopped    N/A             N/A                  
10.70.37.43     MASTER        /rhs/brick2/b5    root          ssh://10.70.37.52::SLAVE    N/A           Stopped    N/A             N/A                  
[root@dhcp37-88 scripts]# gluster volume list
MASTER
gluster_shared_storage
[root@dhcp37-88 scripts]# 



Version-Release number of selected component (if applicable):
=============================================================

glusterfs-3.7.9-7


How reproducible:
=================
Always


Steps to Reproduce:
===================
1. Create geo-rep session between master and slave
2. Stop geo-rep session
3. Stop volume

Actual results:
===============

It fails complaining that the geo-rep session is active. 

Expected results:
=================
Volume stop should succeed

Comment 3 Kotresh HR 2016-06-03 09:10:39 UTC

Upstream Patch:
http://review.gluster.org/#/c/14636/1 (master)

Comment 6 Kotresh HR 2016-06-03 18:34:39 UTC

Upstream Patches:
http://review.gluster.org/14636 (master)
http://review.gluster.org/14637 (3.7) 
http://review.gluster.org/14645 (3.8)

Downstream Patch:
https://code.engineering.redhat.com/gerrit/#/c/75887/

Comment 8 Rahul Hinduja 2016-06-04 07:11:05 UTC

Verified with build: glusterfs-3.7.9-8

Stopping volume when geo-replication is in stopped state is successful. Moving this BZ to verified state.

Comment 11 errata-xmlrpc 2016-06-23 05:25:43 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1240