Bug 1157393

Summary:	mount fails for nfs protocol in rdma volumes
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Jiffin <jthottan>
Component:	gluster-nfs	Assignee:	Jiffin <jthottan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.0	CC:	ndevos
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-20 10:59:15 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:	1157381
Bug Blocks:

Description Jiffin 2014-10-27 07:28:27 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 3 Jiffin 2015-01-20 10:59:15 UTC

It is fixed in current release, they use different bug id is used BZ:1154617,
https://bugzilla.redhat.com/show_bug.cgi?id=1154617