Bug 1524816

Summary:	heketi was not removing the LVs associated with Bricks removed when Gluster Volumes were deleted
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	changetimerecorder	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	abhishku, amukherj, bugs, dwojslaw, ekuric, hchiramm, jcall, kaushal, madam, moagrawa, olim, rhinduja, rhs-bugs, rtalur, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	brick-multiplexing
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1524336	Environment:
Last Closed:	2018-03-15 11:23: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:
Bug Depends On:
Bug Blocks:	1524336

Comment 1 Atin Mukherjee 2017-12-12 08:43:24 UTC

Please have a public bugzilla description captured.

Comment 2 Kaushal 2017-12-13 05:23:21 UTC

Here's a summary of the bug description and analysis.

Heketi sometimes fails to delete the underlying LVs that formed the bricks, when it deletes a volume. This happens because the multiplexed brick process, doesnot correctly stop the brick graph, and leaves open a few files on the brick filesystem. This prevents the brick filesystem from being unmounted, and the LV from being destroyed.

The open files in question, as possibly of the CTR xlator.

Comment 3 Worker Ant 2017-12-13 13:25:14 UTC

COMMIT: https://review.gluster.org/19025 committed in master by \"MOHIT AGRAWAL\" <moagrawa> with a commit message- features/changelog: changelog threads are not cleaned properly after receive GF_EVENT_CLEANUP

Problem: changelog threads are not cleaned properly after receive
         GF_EVENT_CLEANUP while brick mux is enabled

Solution: change changelog notify code path to cleanup threads
          properly

BUG: 1524816
Change-Id: I007f4e14e3d557707df738faf222b78c793d5ab5
Signed-off-by: Mohit Agrawal <moagrawa>

Comment 4 Shyamsundar 2018-03-15 11:23:27 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/