Bug 1350327

Summary:	Protocol client not mounting volumes running on older versions.
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	protocol	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1350326	Environment:
Last Closed:	2017-03-27 18:14:00 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:
Bug Depends On:	1350326
Bug Blocks:

Description Avra Sengupta 2016-06-27 07:13:46 UTC

+++ This bug was initially created as a clone of Bug #1350326 +++

Description of problem:
The 3.8 client expects a child_up key from the server indicating the status of the server translators. This key is not being sent by the servers running older versions, thereby breaking compatibility.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2016-06-27 07:15:43 UTC

REVIEW: http://review.gluster.org/14810 (protocol/server: Fix client/server compatibility) posted (#1) for review on release-3.8 by Avra Sengupta (asengupt)

Comment 2 Vijay Bellur 2016-06-27 07:22:56 UTC

REVIEW: http://review.gluster.org/14811 (protocol/server: Fix client/server compatibility) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 3 Vijay Bellur 2016-06-28 20:27:26 UTC

COMMIT: http://review.gluster.org/14811 committed in master by Jeff Darcy (jdarcy) 
------
commit 10fa1bcce3b73f630dbc3241722c1af9dee4c414
Author: Avra Sengupta <asengupt>
Date:   Mon Jun 27 12:40:17 2016 +0530

    protocol/server: Fix client/server compatibility
    
    The 3.8 client expects a child_up key from the server
    indicating the status of the server translators. This
    key is not being sent by the servers running older
    versions, thereby breaking compatibility.
    
    With this patch we are treating the absence of the said
    key as an indication that the server trying to connect
    to this client is running an older version and hence
    in such a case we are setting conf->child_up as
    _gf_true explicitly. This should suffice in emulating
    the older behavior.
    
    Due to the nature of this bug, requiring two version to
    be reproducible, there are no testcases added for the same.
    
    Change-Id: I29e0a5c63b55380dc9db8e42852d7e95b64a2b2e
    BUG: 1350327
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/14811
    Reviewed-by: Raghavendra G <rgowdapp>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.org>

Comment 4 Shyamsundar 2017-03-27 18:14:00 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.9.0, please open a new bug report.

glusterfs-3.9.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://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/