Bug 1217935

Summary:	[Backup]: To capture path for deletes in changelog file
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	glusterfind	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	avishwan, bugs, khiremat, sanandpa
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1214561	Environment:
Last Closed:	2015-05-14 17:29:33 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:	1214561, 1218383
Bug Blocks:	1186580, 1199352

Description Kotresh HR 2015-05-03 07:07:25 UTC

+++ This bug was initially created as a clone of Bug #1214561 +++

Description of problem:

Glusterfind API presently is just able to mention the files which have been newly created, or have had data/metadata changes. In case a file is deleted, it is not able to get that information from the changelog file

This bug is to track the progress made on that front.

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

Glusterfs 3.7 upstream

How reproducible: Always

Steps to Reproduce:

1. Have a gluster volume of type distribute/replicate
2. Create 2 files 'file1' and 'file2'
3. Edit the contents of 'file2' 
4. Delete 'file2'
5. Change the permissions of 'file1' to (say) read-only
6. Verify the contents of changelog file.

Actual results:

Step 6 should shows Entry operations for 'file1' and 'file2', followed with Data operation for 'file2', and a Metadata operation for 'file1'
Delete operation of 'file2' (step4) is not recorded in the changelog file.

Expected results:

Delete operation of 'file2' should get recorded in the changelog file, which in turn can be used by Glusterfind.

Comment 1 Anand Avati 2015-05-03 07:12:11 UTC

REVIEW: http://review.gluster.org/10500 (geo-rep: Changes required as part of changelog version 1.2) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)

Comment 2 Anand Avati 2015-05-04 18:23:16 UTC

COMMIT: http://review.gluster.org/10500 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit 4e576b97f0c5b636f2e6490371408ebc18c97f6d
Author: Kotresh HR <khiremat>
Date:   Thu Apr 23 10:18:49 2015 +0530

    geo-rep: Changes required as part of changelog version 1.2
    
    The index value for UNLINK and RMDIR in changelog
    is no more the last index. It varies based on whether
    the 'changelog.capture-del-path' is enabled or not.
    Hence, fixed index is used.
    
    The option to capture deleted path in changelog comes
    with the patch: http://review.gluster.org/#/c/10288/
    And the parser changes with http://review.gluster.org/#/c/10166/
    
    BUG: 1217935
    Change-Id: I6d8a941129416381e24226faed9803f7e5fae8d0
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/10344
    Reviewed-on: http://review.gluster.org/10500
    Tested-by: NetBSD Build System
    Reviewed-by: Aravinda VK <avishwan>
    Tested-by: Gluster Build System <jenkins.com>

Comment 3 Niels de Vos 2015-05-14 17:29:33 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Niels de Vos 2015-05-14 17:35:58 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:38:19 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:47:00 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user