Bug 1699715 - Log level changes do not take effect until the process is restarted
Summary: Log level changes do not take effect until the process is restarted
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: 6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1695081
Blocks: 1696046
TreeView+ depends on / blocked
 
Reported: 2019-04-15 04:36 UTC by Mohit Agrawal
Modified: 2019-04-22 13:33 UTC (History)
8 users (show)

Fixed In Version: glusterfs-6.1
Clone Of: 1695081
Environment:
Last Closed: 2019-04-16 11:00:10 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22564 0 None Merged core: Log level changes do not effect on running client process 2019-04-16 11:00:09 UTC

Comment 1 Worker Ant 2019-04-15 05:08:54 UTC 
REVIEW: https://review.gluster.org/22564 (core: Log level changes do not effect on running client process) posted (#2) for review on release-6 by MOHIT AGRAWAL
Comment 2 Worker Ant 2019-04-15 05:12:09 UTC 
REVIEW: https://review.gluster.org/22564 (core: Log level changes do not effect on running client process) posted (#4) for review on release-6 by MOHIT AGRAWAL
Comment 3 Worker Ant 2019-04-16 11:00:10 UTC 
REVIEW: https://review.gluster.org/22564 (core: Log level changes do not effect on running client process) merged (#5) on release-6 by Shyamsundar Ranganathan
Comment 4 Shyamsundar 2019-04-22 13:33:17 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-6.1, please open a new bug report.

glusterfs-6.1 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] https://lists.gluster.org/pipermail/announce/2019-April/000124.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.