Bug 1706776 - maintain consistent values across for options when fetched at cluster level or volume level
Summary: maintain consistent values across for options when fetched at cluster level o...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: cli
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: RHGS 3.5.0
Assignee: Atin Mukherjee
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On: 1707700
Blocks: 1696807
TreeView+ depends on / blocked
 
Reported: 2019-05-06 09:54 UTC by Nag Pavan Chilakam
Modified: 2019-10-30 12:22 UTC (History)
5 users (show)

Fixed In Version: glusterfs-6.0-3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1707700 (view as bug list)
Environment:
Last Closed: 2019-10-30 12:21:23 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:21:41 UTC

Description Nag Pavan Chilakam 2019-05-06 09:54:28 UTC
Description of problem:
=====================
A few options are showing different values when they are fetched at cluster level as against volume level.
A consistent representation would be nice to have
eg: 

[root@dhcp42-80 ~]# gluster v get test350 all|egrep "cluster.server-quorum-ratio|cluster.enable-shared-storage|cluster.op-version|cluster.max-op-version|cluster.brick-multiplex|cluster.max-bricks-per-process|glusterd.vol_count_per_thread|cluster.daemon-log-level"
cluster.server-quorum-ratio             0                                       
cluster.enable-shared-storage           disable                                 
cluster.brick-multiplex                 off                                     
glusterd.vol_count_per_thread           100                                     
cluster.max-bricks-per-process          250                                     
cluster.daemon-log-level                INFO                                    
[root@dhcp42-80 ~]# gluster v get all all
Option                                  Value                                   
------                                  -----                                   
cluster.server-quorum-ratio             51                                      
cluster.enable-shared-storage           disable                                 
cluster.op-version                      70000                                   
cluster.max-op-version                  70000                                   
cluster.brick-multiplex                 disable                                 
cluster.max-bricks-per-process          250                                     
glusterd.vol_count_per_thread           100                                     
cluster.daemon-log-level                INFO                                    



In above example below are the descrepencies

1)It can be seen that "cluster.server-quorum-ratio"at cluster level shows 51% as against 0 at volume level
2)  and "cluster.brick-multiplex  " shows disable at cluster level as against off at volume level--> though both are effectively same, it would be good to either use disable or off at both places. No functional impact, and more of a cosmetic issue


Version-Release number of selected component (if applicable):
================
6.0.2 rhgs3.5

How reproducible:
================
always

Comment 10 errata-xmlrpc 2019-10-30 12:21:23 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://access.redhat.com/errata/RHEA-2019:3249


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