Bug 1380689

Summary: hc.conf should contain volume options for the new features going to be supported for HCI
Product: Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: gdeployAssignee: Devyani Kota <dkota>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.2CC: amukherj, knarra, rcyriac, rhs-bugs, smohan, storage-qa-internal, surs
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:35:02 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    

Description RamaKasturi 2016-09-30 10:46:22 UTC
Description of problem:
HCI is going to support new features for G.A which is granual-entry-selfheal, compound-fops and SSL. As part of this new volume options needs to be added to hc.conf. Options are :

cluster.granular-entry-heal  = on
cluster.use-compound-fops = on
auth.ssl-allow = ‘server1,server2..serverN
client.ssl = on
server.ssl = on

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
New volume options are not present as of now.

Expected results:
Volume options listed in the description should be added to hc.conf and 'gluster volume info <vol_name>' should list them.

Additional info:

Comment 2 Sachidananda Urs 2016-11-03 10:42:29 UTC
Kasturi,

(In reply to RamaKasturi from comment #0)
> Description of problem:
> HCI is going to support new features for G.A which is
> granual-entry-selfheal, compound-fops and SSL. As part of this new volume
> options needs to be added to hc.conf. Options are :
> 
> cluster.granular-entry-heal  = on
> cluster.use-compound-fops = on
> auth.ssl-allow = ‘server1,server2..serverN
> client.ssl = on
> server.ssl = on
> 

I think we do not need the options below:

auth.ssl-allow = ‘server1,server2..serverN
client.ssl = on
server.ssl = on

since these things are taken care of when ssl is enabled
using gdeploy. Is there any need to enable this options without
the need of using SSL?

Comment 3 RamaKasturi 2016-11-03 10:55:15 UTC
(In reply to Sachidananda Urs from comment #2)
> Kasturi,
> 
> (In reply to RamaKasturi from comment #0)
> > Description of problem:
> > HCI is going to support new features for G.A which is
> > granual-entry-selfheal, compound-fops and SSL. As part of this new volume
> > options needs to be added to hc.conf. Options are :
> > 
> > cluster.granular-entry-heal  = on
> > cluster.use-compound-fops = on
> > auth.ssl-allow = ‘server1,server2..serverN
> > client.ssl = on
> > server.ssl = on
> > 
> 
> I think we do not need the options below:
> 
> auth.ssl-allow = ‘server1,server2..serverN
> client.ssl = on
> server.ssl = on
> 
> since these things are taken care of when ssl is enabled
> using gdeploy. Is there any need to enable this options without
> the need of using SSL?

sac,okay. Agree that these options are not required if they are set during SSL enablement using gdeploy.

Comment 4 Devyani Kota 2016-11-03 11:49:26 UTC
Hi,
Here is the commit: https://github.com/gluster/gdeploy/commit/68b1f99300
This solves the issue.
Hence, changing status of the issue.
Thanks.

Comment 7 RamaKasturi 2016-12-08 17:04:21 UTC
verified and works fine with build gdeploy-2.0.1-6.el7rhgs.noarch. I see that values cluster.granular-entry-heal,cluster.use-compound-fops are set on the volumes through gdeploy.

Comment 9 errata-xmlrpc 2017-02-07 11:35:02 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