Bug 1334994

Summary: Fix the message ids in Client
Product: [Community] GlusterFS Reporter: Poornima G <pgurusid>
Component: loggingAssignee: Poornima G <pgurusid>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.8.0CC: 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 14:06:02 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 Poornima G 2016-05-11 05:46:02 UTC
Description of problem:
The message IDs of PC_MSG_GFID_NULL changed as a part of some patch.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Poornima G 2016-05-11 05:47:34 UTC
Fix posted at http://review.gluster.org/#/c/14280/

Comment 2 Vijay Bellur 2016-05-15 07:10:25 UTC
REVIEW: http://review.gluster.org/14280 (client: Fix the message ids) posted (#2) for review on release-3.8 by Niels de Vos (ndevos)

Comment 3 Vijay Bellur 2016-05-15 11:04:15 UTC
COMMIT: http://review.gluster.org/14280 committed in release-3.8 by Niels de Vos (ndevos) 
------
commit ef002764c8ec05d1ca7b658533250a588d0b8609
Author: Poornima G <pgurusid>
Date:   Tue May 10 02:35:22 2016 -0400

    client: Fix the message ids
    
    The message id of PC_MSG_GFID_NULL was changed as a part of rebase
    of http://review.gluster.org/#/c/11597. Fixing the same
    
    Backport of http://review.gluster.org/#/c/14276/
    
    Cherry picked from commit f3699f32fd8d468f757697fdacf4949b8d5312d5
    > Change-Id: I773e02fb5695b6b55700046f4a4298ec475f8991
    > Signed-off-by: Poornima G <pgurusid>
    > Reviewed-on: http://review.gluster.org/14276
    > Smoke: Gluster Build System <jenkins.com>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    > CentOS-regression: Gluster Build System <jenkins.com>
    
    Change-Id: I773e02fb5695b6b55700046f4a4298ec475f8991
    BUG: 1334994
    Signed-off-by: Poornima G <pgurusid>
    Reviewed-on: http://review.gluster.org/14280
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>
    Smoke: Gluster Build System <jenkins.com>

Comment 4 Niels de Vos 2016-06-16 14:06:02 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