Bug 916375

Summary:	Incomplete NLMv4 spec compliance: asynchronous requests and responses
Product:	[Community] GlusterFS	Reporter:	Anand Avati <aavati>
Component:	nfs	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, chrisw, gluster-bugs, ndevos, vagarwal
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-22 15:46:38 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 Anand Avati 2013-02-27 23:18:25 UTC

There was at least one NFS client in the NFS connectathon event which would fail in the locking test. This was diagnosed to be because gluster's NLM does not implement the TEST_MSG procedure.

Comment 1 Anand Avati 2013-02-27 23:19:15 UTC

To be clear, it is the lack of the full set of *_MSG procedures. The failure is visible upfront in the TEST_MSG procedure.

Comment 2 Niels de Vos 2014-12-14 21:04:33 UTC

The *_MSG procedures are for the asynchronous requests and responses.

The procedures are documented here:
- http://pubs.opengroup.org/onlinepubs/009629799/chap10.htm#tagcjh_11_03

Comment 4 Kaleb KEITHLEY 2015-10-22 15:46:38 UTC

because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.