Bug 1158831

Summary:	gnfs : nfs mount fails if the connection between nfs server and bricks is not established
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	nfs	Assignee:	Jiffin <jthottan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	anoopcs, bugs, gluster-bugs, jthottan, ndevos, rgowdapp, rkavunga
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-14 17:28: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:

Description Jiffin 2014-10-30 10:30:33 UTC

Description of problem:

Connection between gluster nfs and brick requires time (especially for rdma).So during that time when we try to mount using nfs ,it will fail saying that volume not found.

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

How reproducible:
Some times. It will depends on no of bricks and protocol

Comment 1 Anand Avati 2014-10-30 10:40:01 UTC

REVIEW: http://review.gluster.org/9011 (gNFS : nfs mount fails if connection between nfs server and        brick process is not established.) posted (#1) for review on master by jiffin tony Thottan (jthottan)

Comment 2 Anand Avati 2014-10-31 03:38:55 UTC

REVIEW: http://review.gluster.org/9011 (gNFS : mount fails if connection to brick(s) is not established yet.) posted (#2) for review on master by jiffin tony Thottan (jthottan)

Comment 3 Anand Avati 2014-10-31 08:14:07 UTC

COMMIT: http://review.gluster.org/9011 committed in master by Niels de Vos (ndevos) 
------
commit a718a11a1c21c1f74460b61c98579db4ae2747ac
Author: jiffin <jthottan>
Date:   Thu Oct 30 15:58:56 2014 +0530

    gNFS : mount fails if connection to brick(s) is not established yet.
    
           Connection between gluster-nfs and brick process requires
           time (especially for rdma).During that time when we try to
           mount using nfs ,it will fail saying that volume not found.
           So we need a check using 'is_nfs_export_available'before
           mounting to ensure volume is available.This patch will provide
           the check before nfs mount if it is not given in the test files
    
    Change-Id: I242eb6e3118ebaca1df46314302a203a0c9738a8
    BUG: 1158831
    Signed-off-by: jiffin tony thottan <jthottan>
    Reviewed-on: http://review.gluster.org/9011
    Reviewed-by: Meghana M <mmadhusu>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>

Comment 4 Niels de Vos 2015-05-14 17:28:15 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 5 Niels de Vos 2015-05-14 17:35:40 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 6 Niels de Vos 2015-05-14 17:38:03 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 7 Niels de Vos 2015-05-14 17:44:21 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