Bug 761758 (GLUSTER-26)

Summary:	Version mismatch not handled correctly
Product:	[Community] GlusterFS	Reporter:	Gururaj K <guru>
Component:	protocol	Assignee:	Vijay Bellur <vbellur>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	2.0.2	CC:	amarts, gluster-bugs, rabhat
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTNR	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Gururaj K 2009-06-17 12:49:27 UTC

* Tried connecting 2.0.2 client with 2.0.0 server
* The remote volume was mounted without errors, but when tried to access, got a "Transport endpoint .."


With NORMAL level logging, the following message is printed (REPEATEDLY):
[2009-06-17 17:50:01] W [fuse-bridge.c:395:fuse_entry_cbk] glusterfs-fuse: 6: LOOKUP() / => -1 (Transport endpoint is not connected)


DEBUG level logging reveals more:
[2009-06-17 17:49:56] D [client-protocol.c:5508:client_setvolume_cbk] share: failed to get 'process-uuid' from reply dictionary
[2009-06-17 17:49:56] D [client-protocol.c:5514:client_setvolume_cbk] share: SETVOLUME on remote-host failed: Version mismatch: client(2.0.2) Vs server (2.0.0)


Note that the log level is "D". The client does not error out once the mismatch has been detected.

Comment 1 Anand Avati 2009-11-26 07:48:53 UTC

PATCH: http://patches.gluster.com/patch/2379 in master (changed the log level of failure case in client_setvolume_cbk)