Bug 1567110

Summary:	Make cluster.localtime-logging not to be visible in gluster v get
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED ERRATA	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	rhinduja, rhs-bugs, storage-qa-internal, vbellur
Target Milestone:	---
Target Release:	RHGS 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.2-8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 06:46:01 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1503137

Description Atin Mukherjee 2018-04-13 12:50:11 UTC

Description of problem:

Given cluster.localtime-logging feature (RFE BZ 958062) isn't complete yet in RHGS 3.4.0 as when enabled all the logs don't follow the same local timezone. Reverting the entire code causes too much of merge conflict and the best possible way is to make it disappear from the gluster volume get command so that user doesn't get to see this option.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 6 Bala Konda Reddy M 2018-04-23 06:47:58 UTC

Build : 3.12.2-8

The option is not visible in gluster vol get <all> <all> and gluster vol get <volname> all

Hence marking as verified

Comment 8 errata-xmlrpc 2018-09-04 06:46:01 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/RHSA-2018:2607