Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1237000

Summary:	Add a test case for verifying NO empty changelog created
Product:	[Community] GlusterFS	Reporter:	Saravanakumar <sarumuga>
Component:	geo-replication	Assignee:	Saravanakumar <sarumuga>
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-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-16 13:17:51 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 Saravanakumar 2015-06-30 07:24:00 UTC

Description of problem:
Empty changelogs are no longer created over changelog roll-over period.
Add a test case to verify the same.

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


How reproducible:
Create a volume
Start a volume.
Turn on changelog.
Wait for changelog rollover time duration.
No NEW changelog should get created over changelog rollover period.

Steps to Reproduce:
1.Create a volume
2.Start a volume.
3.Turn on changelog.
4.wait for changelog rollover time duration.
5.No NEW changelog should get created over changelog rollover period.

Actual results:
No NEW changelog should get created  over changelog rollover period.

Expected results:
Test case should pass.

Additional info:

The actual bug is actually fixed in Bug#1208470. 
This is mainly for adding a test case for the same.

Comment 1 Anand Avati 2015-06-30 07:25:17 UTC

REVIEW: http://review.gluster.org/11460 (changelog: test case for verifying empty changelogs avoided) posted (#1) for review on master by Saravanakumar Arumugam (sarumuga)

Comment 2 Anand Avati 2015-07-07 13:26:49 UTC

REVIEW: http://review.gluster.org/11460 (changelog: test case for verifying empty changelogs avoided) posted (#2) for review on master by Saravanakumar Arumugam (sarumuga)

Comment 3 Anand Avati 2015-07-14 05:39:19 UTC

REVIEW: http://review.gluster.org/11460 (changelog: test case for verifying empty changelogs avoided) posted (#3) for review on master by Saravanakumar Arumugam (sarumuga)

Comment 4 Anand Avati 2015-07-20 07:03:35 UTC

REVIEW: http://review.gluster.org/11460 (changelog: test case for verifying empty changelogs avoided) posted (#4) for review on master by Venky Shankar (vshankar)

Comment 5 Anand Avati 2015-07-22 04:01:04 UTC

REVIEW: http://review.gluster.org/11460 (changelog: test case for verifying empty changelogs avoided) posted (#5) for review on master by Venky Shankar (vshankar)

Comment 6 Niels de Vos 2016-06-16 13:17:51 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