Bug 1386578

Summary:	mounting with rdma protocol fails for tcp,rdma volumes
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	protocol	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
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 Mohammed Rafi KC 2016-10-19 09:11:37 UTC

Description of problem:

When trying to mount tcp,rdma type volume using rdma protocol, mount always fails

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


How reproducible:


Steps to Reproduce:
1.create tcp,rdma volume
2.start the volume
3.mount the volume using rdma protocol

Actual results:

mount failed

Expected results:

mount should't fail

Additional info:

Comment 1 Worker Ant 2016-10-20 13:19:11 UTC

REVIEW: http://review.gluster.org/15687 (protocol/mgmt: sending wrong return value during emancipation) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

Comment 2 Worker Ant 2016-11-09 06:42:07 UTC

REVIEW: http://review.gluster.org/15687 (protocol/mgmt: sending wrong return value during emancipation) posted (#2) for review on master by mohammed rafi  kc (rkavunga)

Comment 3 Worker Ant 2017-02-27 05:52:54 UTC

COMMIT: https://review.gluster.org/15687 committed in master by Raghavendra G (rgowdapp) 
------
commit 8aee74f25cfa9dc676e116e9882723254b0509a9
Author: Mohammed Rafi KC <rkavunga>
Date:   Wed Oct 19 15:20:45 2016 +0530

    protocol/mgmt: sending wrong return value during emancipation
    
    A change introduced for moving emancipation after signin process
    cause this regression, where the second signin always return the
    size of process xdr.
    
    This patch will fix the issue.
    
    Change-Id: Ic924c82abe6932a93abe37df1fd2d1285a77ed0a
    BUG: 1386578
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: https://review.gluster.org/15687
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>

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/