Bug 1509254

Summary:	snapshot remove does not cleans lvm for deactivated snaps
Product:	[Community] GlusterFS	Reporter:	Sunny Kumar <sunkumar>
Component:	snapshot	Assignee:	Sunny Kumar <sunkumar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-15 11:19:42 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 Sunny Kumar 2017-11-03 12:11:15 UTC

Description of problem:
During snapshot remove lvm cleanup was skipped for deactivated snapshots.


How reproducible:
Always

Steps to Reproduce:
1. create snapshot
2. remove deactivated snapshot
3. check for lvm details

Actual results:
Does not cleans lvm for deleted snaps

Expected results:
Should clean lvm for deleted snaps

Additional info:

LVM cleanup is working in case of activated snap delete.

Comment 1 Worker Ant 2017-11-03 12:19:06 UTC

REVIEW: https://review.gluster.org/18654 (snapshot: lvm cleanup during snapshot remove) posted (#1) for review on master by Sunny Kumar

Comment 2 Worker Ant 2017-11-08 05:21:58 UTC

COMMIT: https://review.gluster.org/18654 committed in master by  

------------- snapshot: lvm cleanup during snapshot remove

Problem : During snapshot remove lvm cleanup was skipped for deactivated
          snapshots by assuming that its mount point is not present.

Fix : Do no skip lvm cleanup by checking active mount point.

Change-Id: I856d2d647c75db8b37b7f430277daef6eb7580a8
BUG: 1509254
Signed-off-by: Sunny Kumar <sunkumar>

Comment 3 Shyamsundar 2018-03-15 11:19:42 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-4.0.0, please open a new bug report.

glusterfs-4.0.0 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://lists.gluster.org/pipermail/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/