Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1447604

Summary:	volume set fails if nfs.so is not installed
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.11	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.11.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-30 18:51:45 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 Atin Mukherjee 2017-05-03 10:00:58 UTC

Description of problem:
volume set fails if nfs.so is not installed

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-05-03 10:01:56 UTC

REVIEW: https://review.gluster.org/17156 (glusterd: skip nfs svc reconfigure if nfs xlator is not installed) posted (#1) for review on release-3.11 by Atin Mukherjee (amukherj)

Comment 2 Worker Ant 2017-05-07 15:33:47 UTC

COMMIT: https://review.gluster.org/17156 committed in release-3.11 by Shyamsundar Ranganathan (srangana) 
------
commit 714e5505b036f708a4594473d475dbe2c94494ec
Author: Atin Mukherjee <amukherj>
Date:   Tue May 2 11:46:11 2017 +0530

    glusterd: skip nfs svc reconfigure if nfs xlator is not installed
    
    With 83abcba, nfs svc is not (re)started or stopped if NFS so file is
    not installed. However the same check was missing in nfs svc reconfigure
    which was causing all volume set command to fail.
    
    >Reviewed-on: https://review.gluster.org/17149
    >Smoke: Gluster Build System <jenkins.org>
    >NetBSD-regression: NetBSD Build System <jenkins.org>
    >Reviewed-by: Niels de Vos <ndevos>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Jeff Darcy <jeff.us>
    >(cherry picked from commit 316e3300cfaa646b7fa45fcc7f57b81c7bb15a0e)
    
    Change-Id: Ie87b5dba44ac59e890cbd60f85944f8e685ad52b
    BUG: 1447604
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: https://review.gluster.org/17156
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana>

Comment 3 Shyamsundar 2017-05-30 18:51:45 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.11.0, please open a new bug report.

glusterfs-3.11.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/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/