Bug 1350371 - ganesha/glusterd : remove 'HA_VOL_SERVER' from ganesha-ha.conf
Summary: ganesha/glusterd : remove 'HA_VOL_SERVER' from ganesha-ha.conf
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: ganesha-nfs
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiffin
QA Contact:
URL:
Whiteboard:
Depends On: 1348954
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-27 09:59 UTC by Jiffin
Modified: 2017-03-27 18:27 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.9.0
Clone Of: 1348954
Environment:
Last Closed: 2017-03-27 18:27:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Jiffin 2016-06-27 09:59:16 UTC
+++ This bug was initially created as a clone of Bug #1348954 +++

Description of problem:

The 'HA_VOL_SERVER' is not needed anymore for the ganesha-ha setup. It looks confusing for the customer. But  variable was internally used in gluster code.
We also need to remove it from there as well.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-06-22 19:41:48 EDT ---

This bug is automatically being proposed for the current z-stream release of Red Hat Gluster Storage 3 by setting the release flag 'rhgs‑3.1.z' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

Comment 1 Vijay Bellur 2016-06-27 10:00:01 UTC
REVIEW: http://review.gluster.org/14812 (ganesha/scripts : remove 'HA_VOL_SERVER' from the code) posted (#1) for review on master by jiffin tony Thottan (jthottan)

Comment 2 Vijay Bellur 2016-06-28 11:58:19 UTC
REVIEW: http://review.gluster.org/14812 (ganesha/scripts : remove 'HA_VOL_SERVER' from the code) posted (#2) for review on master by jiffin tony Thottan (jthottan)

Comment 3 Vijay Bellur 2016-08-08 09:25:09 UTC
REVIEW: http://review.gluster.org/14812 (ganesha/scripts : remove 'HA_VOL_SERVER' from the code) posted (#3) for review on master by jiffin tony Thottan (jthottan)

Comment 4 Worker Ant 2016-08-25 08:37:38 UTC
REVIEW: http://review.gluster.org/14812 (ganesha/scripts : remove 'HA_VOL_SERVER' from the code) posted (#4) for review on master by jiffin tony Thottan (jthottan)

Comment 5 Worker Ant 2016-08-26 05:54:04 UTC
COMMIT: http://review.gluster.org/14812 committed in master by Atin Mukherjee (amukherj) 
------
commit 79e9aa5d7a24275f857d2cf23f910f63c53e9d4e
Author: Jiffin Tony Thottan <jthottan>
Date:   Mon Jun 27 15:08:25 2016 +0530

    ganesha/scripts : remove 'HA_VOL_SERVER' from the code
    
    The parameter HA_VOL_SERVER introduced intially ganesha-ha.conf to
    specify gluster server from which to mount the shared data volume.
    But after introducing new cli for the same purpose, it become
    unnecessary. The existence of that parameter can lead confussion
    to the users. This patch will remove/replace all the instance of
    HA_VOL_SERVER from the code
    
    Change-Id: I638c61dcd2c21ebdb279bbb141d35bb806bd3ef0
    BUG: 1350371
    Signed-off-by: Jiffin Tony Thottan <jthottan>
    Reviewed-on: http://review.gluster.org/14812
    Tested-by: Kaleb KEITHLEY <kkeithle>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: soumya k <skoduri>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 6 Shyamsundar 2017-03-27 18:27:08 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/


Note You need to log in before you can comment on or make changes to this bug.