Bug 1384989

Summary: libglusterfs : update correct memory segments in glfs-message-id
Product: [Community] GlusterFS Reporter: Muthu Vigneshwaran <mvignesh>
Component: libglusterfsclientAssignee: Muthu Vigneshwaran <mvignesh>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.11.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-30 18:35:29 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 Muthu Vigneshwaran 2016-10-14 13:56:02 UTC
Description of problem:

In glfs-message-id the memory segment for JBR are not allocated properly.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2016-10-14 15:05:52 UTC
REVIEW: http://review.gluster.org/15644 (libglusterfs : update correct memory segments in glfs-message-id) posted (#1) for review on master by Muthu Vigneshwaran

Comment 2 Worker Ant 2016-11-18 09:32:30 UTC
REVIEW: http://review.gluster.org/15644 (libglusterfs : update correct message segments in glfs-message-id) posted (#2) for review on master by Muthu Vigneshwaran

Comment 3 Worker Ant 2017-03-14 02:57:08 UTC
COMMIT: https://review.gluster.org/15644 committed in master by Vijay Bellur (vbellur) 
------
commit 870a1d66f56345df38b70baa31ae314e2cde789c
Author: mvignesh <mvignesh>
Date:   Fri Oct 14 19:38:21 2016 +0530

    libglusterfs : update correct message segments in glfs-message-id
    
    Change-Id: I6611c5699303c879e6f5d88549f5101dd6f63e46
    BUG: 1384989
    Signed-off-by: Muthu-vigneshwaran <mvignesh>
    Reviewed-on: https://review.gluster.org/15644
    Tested-by: Muthu Vigneshwaran <muthuvigneshwaran77>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 4 Shyamsundar 2017-05-30 18:35:29 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.11.0, please open a new bug report.

glusterfs-3.11.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://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/