Red Hat Bugzilla – Bug 1380689
hc.conf should contain volume options for the new features going to be supported for HCI
Last modified: 2017-03-07 12:45:52 EST
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:
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?
(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.
Hi, Here is the commit: https://github.com/gluster/gdeploy/commit/68b1f99300 This solves the issue. Hence, changing status of the issue. Thanks.
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.
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