Bug 1380315

Summary:	nfs.disable=on option can be removed from hc.conf file
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	gdeploy	Assignee:	Sachidananda Urs <surs>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	amukherj, rcyriac, rhinduja, rhs-bugs, smohan, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.3 Async
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gdeploy-2.0.1-5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-07 11:34:54 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:
Bug Blocks:	1351528

Description RamaKasturi 2016-09-29 09:34:15 UTC

Description of problem:
From RHGS3.2 nfs.disable=on will be set on the newly created volumes by default.It is no longer required to set this option from gdeploy. This option can be removed from hc.conf.

Version-Release number of selected component (if applicable):
gdeploy-2.0-16.el7rhgs.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Remove nfs.disable=on from hc.conf file.

Additional info:

Comment 2 Sachidananda Urs 2016-11-03 08:20:55 UTC

https://github.com/gluster/gdeploy/commit/6ccb932087b3 fixes the issue

Comment 5 RamaKasturi 2016-12-08 14:42:47 UTC

Verified and works fine with build gdeploy-2.0.1-6.el7rhgs.noarch. Checked in the committed code link present at comment 2 i see that nfs.disable=on is not present in hc.conf.

Comment 9 errata-xmlrpc 2017-02-07 11:34:54 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2017-0260.html