Bug 1157381

Summary:	mount fails for nfs protocol in rdma volumes
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	nfs	Assignee:	Jiffin <jthottan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiffin <jthottan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	anoopcs, bugs, gluster-bugs, jthottan, mmadhusu, ndevos, rgowdapp, rkavunga, rtalur, skoduri
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1166505 (view as bug list)		Environment:
Last Closed:	2015-05-14 17:28:06 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:
Bug Blocks:	1157393, 1166505

Description Jiffin 2014-10-27 06:53:35 UTC

Description of problem:

When we mount rdma only volume or tcp,rdma volume using newly peer probed IP's(nfs-server on new nodes) through nfs protocol , mount fails for rdma only volume and mount happens with help of tcp in tcp,rdma volumes.


How reproducible:

Always

Steps to Reproduce:

1.Create a rdma only or tcp,rdma volumes in the cluster
2.Start the volume
3.Peer Probe a new server
4.Try to mount using new nfs-server (new IP)

Actual results:

1. For rdma only volume , mount fails
2. For tcp,rdma volume , mount happens with help of tcp 

Expected results:

1.mount should happen incase of rdma only volume
2.mount should happen with rdma transport type by default if no options are set for nfs.transport-type incase of tcp,rdma volume

Additional info:
nfs-server-volgraph build on newly added server is always contains transport type as tcp(socket).

Comment 1 Anand Avati 2014-10-27 07:23:58 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#1) for review on master by jiffin tony Thottan (jthottan)

Comment 2 Anand Avati 2014-10-27 10:59:48 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#2) for review on master by jiffin tony Thottan (jthottan)

Comment 3 Anand Avati 2014-10-27 12:09:16 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#3) for review on master by jiffin tony Thottan (jthottan)

Comment 4 Anand Avati 2014-10-27 12:20:40 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#4) for review on master by jiffin tony Thottan (jthottan)

Comment 5 Anand Avati 2014-10-28 04:55:17 UTC

REVIEW: http://review.gluster.org/8975 (rdma : mount fails for nfs protocol in rdma volumes) posted (#5) for review on master by jiffin tony Thottan (jthottan)

Comment 6 Anand Avati 2014-11-13 19:16:10 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#6) for review on master by jiffin tony Thottan (jthottan)

Comment 7 Anand Avati 2014-11-17 12:54:53 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#7) for review on master by jiffin tony Thottan (jthottan)

Comment 8 Anand Avati 2014-11-17 13:33:07 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#8) for review on master by jiffin tony Thottan (jthottan)

Comment 9 Anand Avati 2014-11-17 13:35:50 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#9) for review on master by jiffin tony Thottan (jthottan)

Comment 10 Anand Avati 2014-11-18 05:39:39 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#10) for review on master by jiffin tony Thottan (jthottan)

Comment 11 Anand Avati 2014-11-18 09:03:10 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#11) for review on master by jiffin tony Thottan (jthottan)

Comment 12 Anand Avati 2014-11-18 11:01:21 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#12) for review on master by jiffin tony Thottan (jthottan)

Comment 13 Anand Avati 2014-11-18 11:02:54 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#13) for review on master by jiffin tony Thottan (jthottan)

Comment 14 Anand Avati 2014-11-18 12:00:59 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#14) for review on master by jiffin tony Thottan (jthottan)

Comment 15 Anand Avati 2014-11-18 15:19:12 UTC

REVIEW: http://review.gluster.org/8975 (rdma :mount fails for nfs protocol in rdma volumes) posted (#15) for review on master by mohammed rafi  kc (rkavunga)

Comment 16 Anand Avati 2014-11-19 09:44:59 UTC

COMMIT: http://review.gluster.org/8975 committed in master by Niels de Vos (ndevos) 
------
commit f380e2029d608f97e3ba9a728605e1d798b09e8d
Author: Jiffin Tony Thottan <jthottan>
Date:   Tue Oct 21 08:59:46 2014 -0400

    rdma :mount fails for nfs protocol in rdma volumes
    
    When we mount rdma only volume or tcp,rdma volume using newly
    peer probed IP's(nfs-server on new nodes) through nfs protocol,
    mount fails for rdma only volume and mount happens with
    help of tcp protocol in the case of tcp,rdma volumes. That is for
    newly added servers will always get transport type as "socket".
    This is due to nfs_transport_type is exported correctly and
    imported wrongly.
    
    This can be verified by the following ,
       * Create a rdma only volume or tcp,rdma volume
       * Add a new server into the trusted pool.
       * Checkout the client transport type specified nfs-server
         volgraph.It will be always tcp(socket type) instead of rdma.
       * And also for rdma only volume in the nfs log, we can see
         'connection refused' message for every reconnect between
         nfs server and glusterfsd.
    
    BUG: 1157381
    
    Change-Id: I6bd4979e31adfc72af92c1da06a332557b6289e2
    Author:    Jiffin Tony Thottan <jthottan>
    Signed-off-by: Jiffin Tony Thottan <jthottan>
    Reviewed-on: http://review.gluster.org/8975
    Reviewed-by: Meghana M <mmadhusu>
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Niels de Vos <ndevos>
    Tested-by: Niels de Vos <ndevos>

Comment 17 Niels de Vos 2015-05-14 17:28:06 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 18 Niels de Vos 2015-05-14 17:35:39 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 19 Niels de Vos 2015-05-14 17:38:01 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 20 Niels de Vos 2015-05-14 17:44:20 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user