Bug 1493113 - tune loglevel to file gluster-block-configshell.log as INFO from DEBUG
Summary: tune loglevel to file gluster-block-configshell.log as INFO from DEBUG
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-block
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.0
Assignee: Prasanna Kumar Kalever
QA Contact: Sweta Anandpara
URL:
Whiteboard:
: 1493157 (view as bug list)
Depends On:
Blocks: 1417151 1493154
TreeView+ depends on / blocked
 
Reported: 2017-09-19 12:04 UTC by Prasanna Kumar Kalever
Modified: 2017-09-21 04:22 UTC (History)
5 users (show)

Fixed In Version: gluster-block-0.2.1-14.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1493154 (view as bug list)
Environment:
Last Closed: 2017-09-21 04:22:29 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2773 0 normal SHIPPED_LIVE new packages: gluster-block 2017-09-21 08:16:22 UTC

Description Prasanna Kumar Kalever 2017-09-19 12:04:28 UTC 
Description of problem:
$sub

Currently targetcli logs all the commands output sequence to gluster-block-configshell.log in debug mode.

But what we have noticed is while we are trying to scale gluster-block we observed that the logfile is consuming a lot of disk space.

so we need to set the global loglevel_file to info
Comment 4 Atin Mukherjee 2017-09-19 13:41:19 UTC 
*** Bug 1493157 has been marked as a duplicate of this bug. ***
Comment 6 Sweta Anandpara 2017-09-20 11:20:04 UTC 
Checked this on gluster-block-0.2.1-14 and tcmu-runner-1.2.0-15. 

/var/log/gluster-block/gluster-block-configshell.log shows none of the DEBUG level messages, post update.

Moving this bug to verified in rhgs 3.3.0.
Comment 8 errata-xmlrpc 2017-09-21 04:22:29 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-2017:2773
Note You need to log in before you can comment on or make changes to this bug.