Bug 1393204

Summary: Remove 'HA_VOL_SERVER' from ganesha-ha.conf.
Product: Red Hat Gluster Storage Reporter: Arthy Loganathan <aloganat>
Component: gdeployAssignee: Sachidananda Urs <surs>
Status: CLOSED ERRATA QA Contact: Arthy Loganathan <aloganat>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.2CC: amukherj, rcyriac, rhinduja, rhs-bugs, smohan, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.3 Async   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gdeploy-2.0.1-4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-07 11:35:35 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:
Bug Depends On:    
Bug Blocks: 1351528    
Attachments:
Description Flags
sample ganesha-ha.conf file none

Description Arthy Loganathan 2016-11-09 05:37:18 UTC 
Description of problem:
'HA_VOL_SERVER' has been removed from ganesha-ha.conf in the nfs-ganesha build
nfs-ganesha-2.4.1-1.el7rhgs.x86_64. So, we have to do changes in gdeploy to remove 'HA_VOL_SERVER' from ganesha-ha.conf.

There was a bug raised and fixed in nfs-ganesha for the same - https://bugzilla.redhat.com/show_bug.cgi?id=1348954

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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Sample ganesha-ha.conf is attached.
Comment 2 Arthy Loganathan 2016-11-09 05:38:19 UTC 
Created attachment 1218819 [details]
sample ganesha-ha.conf file
Comment 3 Sachidananda Urs 2016-11-10 07:36:15 UTC 
https://github.com/gluster/gdeploy/commit/6c4a803201fe4cebb76c294187f57 fixes the issue.
Comment 7 Arthy Loganathan 2016-11-21 12:10:35 UTC 
Verified the fix in build,

gdeploy-2.0.1-4.el7rhgs.noarch
Comment 9 errata-xmlrpc 2017-02-07 11:35:35 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