Bug 761758 (GLUSTER-26) - Version mismatch not handled correctly
Summary: Version mismatch not handled correctly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-26
Product: GlusterFS
Classification: Community
Component: protocol
Version: 2.0.2
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-17 12:49 UTC by Gururaj K
Modified: 2010-01-28 13:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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)
Note You need to log in before you can comment on or make changes to this bug.