Bug 1310856

Summary:	implement BIND_CONN_TO_SESSION
Product:	[Retired] nfs-ganesha	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	MainNFSD	Assignee:	Frank Filz <ffilz>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.4
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-22 16:00:27 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 Kaleb KEITHLEY 2016-02-22 20:00:51 UTC

Description of problem:

ESXi clients, e.g., try to use BIND_CONN_TO_SESSION.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Kaleb KEITHLEY 2016-02-22 20:12:10 UTC

ESXi clients, e.g., try to use BIND_CONN_TO_SESSION.

If I understood correctly, user mounted from box1 (in a three box cluster).  Then killed box2.  With the gluster HA setup that resulted in two things happening. 1) box2's floating IP moved (to box3?), and 2) box1 and box3's ganesha.nfsd entered NFS-GRACE.  When box1 emerged from grace the ESXi clients' mounts were borked.

A similar setup with Linux clients "survived" the ganesha.nfsd emerging from NFS-GRACE.

It's not clear whether ESXi clients depend on BIND_CONN_TO_SESSION.

Comment 2 Kaleb KEITHLEY 2019-11-22 16:00:27 UTC

looks like BIND_CONN_TO_SESSION is implemented now