Bug 1251449

Summary:	posix_make_ancestryfromgfid doesn't set op_errno
Product:	[Community] GlusterFS	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	quota	Assignee:	Vijaikumar Mallikarjuna <vmallika>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, rgowdapp, smohan, storage-qa-internal
Target Milestone:	---	Keywords:	Reopened, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1251447
Clones:	1253260 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:29: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:
Bug Depends On:	1229621, 1251447
Bug Blocks:	1253260

Comment 1 Anand Avati 2015-08-07 10:27:07 UTC

REVIEW: http://review.gluster.org/11861 (posix: posix_make_ancestryfromgfid shouldn't log ENOENT) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Anand Avati 2015-08-13 10:44:15 UTC

COMMIT: http://review.gluster.org/11861 committed in master by Raghavendra G (rgowdapp) 
------
commit fb4955b796ab2f3236e00686ecc99e792f9c0f8b
Author: vmallika <vmallika>
Date:   Fri Aug 7 15:51:53 2015 +0530

    posix: posix_make_ancestryfromgfid shouldn't log ENOENT
    
    posix_make_ancestryfromgfid shouldn't log ENOENT
    and it should set proper op_errno
    
    Change-Id: I8a87f30bc04d33cab06c91c74baa9563a1c7b45d
    BUG: 1251449
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/11861
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 3 Nagaprasad Sathyanarayana 2015-10-25 14:43:01 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:29: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-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