Bug 1201631

Summary:	Dist-geo-rep: With new Active/Passive switching logic, mgmt volume mountpoint is not cleaned up.
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	avishwan, bugs, gluster-bugs, rkavunga
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-10 03:57:27 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:

Description Kotresh HR 2015-03-13 07:06:43 UTC

Description of problem:
With new Active/Passive switching logic using fcntl lock on a file
residing in shared management volume. The management volume mount
will remain after geo-rep is stopped.

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


How reproducible:
Always

Steps to Reproduce:
1. Setup geo-replication with management volume. 
2. start and stop geo-replication

Actual results:
Management volume mount point remains after geo-rep stop

Expected results:
Management mount point should be unmounted upon geo-rep stop

Additional info:
The management volume mount point choosen is predictable path and it uses
same mount point even after multiple geo-rep stop and start cycles. Hence, there won't be multiple mountpoints left over, it will be only one.

Comment 1 Aravinda VK 2015-05-10 03:57:27 UTC

With patches http://review.gluster.org/#/c/10196/ and http://review.gluster.org/#/c/10458/, Geo-rep is not mounting Meta volume internally. Closing this bug. Please reopen if the issue found again.