Bug 1255310

Summary:	Snapshot: When soft limit is reached, auto-delete is enable, create snapshot doesn't logs anything in log files
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	annair, asengupt, ashah, asrivast, bugs, gluster-bugs, rjoseph, storage-qa-internal
Target Milestone:	---	Keywords:	Reopened, Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1231080
Clones:	1255311 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:33:12 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:	1231080
Bug Blocks:	1223636, 1255311

Comment 1 Anand Avati 2015-08-20 09:23:46 UTC

REVIEW: http://review.gluster.org/11963 (snapshot: Log deletion of snapshot, during auto-delete) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Anand Avati 2015-08-24 06:48:47 UTC

COMMIT: http://review.gluster.org/11963 committed in master by Rajesh Joseph (rjoseph) 
------
commit 69942154e197d753580b74cc7f8e6bce470ee673
Author: Avra Sengupta <asengupt>
Date:   Thu Aug 20 14:40:29 2015 +0530

    snapshot: Log deletion of snapshot, during auto-delete
    
    When auto-delete is enabled, and soft-limit is reached,
    on creation of a snapshot, the oldest snapshot for that
    volume is deleted.
    
    Displaying a warning log before deleting the oldest
    snapshot.
    
    Change-Id: I75f0366935966a223b63a4ec5ac13f9fe36c0e82
    BUG: 1255310
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/11963
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: mohammed rafi  kc <rkavunga>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 3 Nagaprasad Sathyanarayana 2015-10-25 14:50:42 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 4 Niels de Vos 2016-06-16 13:33:12 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.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user