Bug 1563334 - Honour cluster.localtime-logging option for all the daemons
Summary: Honour cluster.localtime-logging option for all the daemons
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 958062
TreeView+ depends on / blocked
 
Reported: 2018-04-03 15:56 UTC by Atin Mukherjee
Modified: 2018-06-20 18:03 UTC (History)
1 user (show)

Fixed In Version: glusterfs-v4.1.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:03:42 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Atin Mukherjee 2018-04-03 15:56:32 UTC
Description of problem:

cluster.localtime-logging option when enabled is reflected in glusterd, bricks and mount logs where as the other daemons like shd, quota, rebalance still follows the UTC.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-04-03 16:07:54 UTC
REVIEW: https://review.gluster.org/19814 (glusterd: honour localtime-logging for all the daemons) posted (#1) for review on master by Atin Mukherjee

Comment 2 Worker Ant 2018-04-04 02:17:41 UTC
COMMIT: https://review.gluster.org/19814 committed in master by "Atin Mukherjee" <amukherj> with a commit message- glusterd: honour localtime-logging for all the daemons

Change-Id: I97a70d29365b0a454241ac5f5cae56d93eefd73a
Fixes: bz#1563334
Signed-off-by: Atin Mukherjee <amukherj>

Comment 3 Shyamsundar 2018-06-20 18:03:42 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report.

glusterfs-v4.1.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/


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