Bug 1175752 - [USS]: On a successful lookup, snapd logs are filled with Warnings "dict OR key (entry-point) is NULL"
Summary: [USS]: On a successful lookup, snapd logs are filled with Warnings "dict OR k...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: snapshot
Version: 3.6.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard: USS
Depends On: 1171132 1172430
Blocks: glusterfs-3.6.2
TreeView+ depends on / blocked
 
Reported: 2014-12-18 14:01 UTC by Vijaikumar Mallikarjuna
Modified: 2016-05-11 22:47 UTC (History)
10 users (show)

Fixed In Version: glusterfs-3.6.2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1172430
Environment:
Last Closed: 2015-02-11 09:09:56 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-12-26 05:28:19 UTC
REVIEW: http://review.gluster.org/9347 (uss/gluster: In SVS, check for entry-point in dict only if inode_ctx is not available) posted (#1) for review on release-3.6 by Sachin Pandit (spandit)

Comment 2 Anand Avati 2015-01-07 14:20:41 UTC
REVIEW: http://review.gluster.org/9347 (uss/gluster: In SVS, check for entry-point in dict only if inode_ctx is not available.) posted (#2) for review on release-3.6 by Sachin Pandit (spandit)

Comment 3 Anand Avati 2015-01-08 09:42:18 UTC
COMMIT: http://review.gluster.org/9347 committed in release-3.6 by Raghavendra Bhat (raghavendra) 
------
commit a0e35d4f09e63fa91737c6abf40a58401590acc7
Author: vmallika <vmallika>
Date:   Thu Dec 11 11:18:03 2014 +0530

    uss/gluster: In SVS, check for entry-point in dict only if inode_ctx is not available.
    
    Change-Id: I990487003b712bf4aed8f54291417965f301655e
    BUG: 1175752
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/9265
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Sachin Pandit <spandit>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/9347
    Reviewed-by: Raghavendra Bhat <raghavendra>

Comment 4 Raghavendra Bhat 2015-02-11 09:09:56 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.6.2, please reopen this bug report.

glusterfs-3.6.2 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should already be or become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

The fix for this bug likely to be included in all future GlusterFS releases i.e. release > 3.6.2.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/5978
[2] http://news.gmane.org/gmane.comp.file-systems.gluster.user
[3] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137


Note You need to log in before you can comment on or make changes to this bug.