Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1567110 - Make cluster.localtime-logging not to be visible in gluster v get
Make cluster.localtime-logging not to be visible in gluster v get
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.4
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.4.0
Assigned To: Atin Mukherjee
Bala Konda Reddy M
:
Depends On:
Blocks: 1503137
  Show dependency treegraph
 
Reported: 2018-04-13 08:50 EDT by Atin Mukherjee
Modified: 2018-09-04 02:47 EDT (History)
4 users (show)

See Also:
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 02:46:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2607 None None None 2018-09-04 02:47 EDT

  None (edit)
Description Atin Mukherjee 2018-04-13 08:50:11 EDT
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 02:47:58 EDT
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 02:46:01 EDT
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

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