tcmu-runner: change loglevel from Err to Info
Description of problem:
++++++++++++++++++++++++
For a Gluster block setup, please change the current logging to include INFO(I) messages as well. Currently, as seen in tcmu-runner-glfs.log as well, only the E messages are getting logged.
E.g
----------------------------------
sh-4.2# tail -f /var/log/glusterfs/gluster-block/tcmu-runner-glfs.log
[2018-08-21 06:44:54.839831] E [MSGID: 114058] [client-handshake.c:1565:client_query_portmap_cbk] 0-vol_9a7f161b2744bbd85b1b3c6b9fe50431-client-1: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.
[2018-08-21 06:46:33.951146] E [MSGID: 114058] [client-handshake.c:1565:client_query_portmap_cbk] 0-vol_9a7f161b2744bbd85b1b3c6b9fe50431-client-1: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.
----------------------------------
Current settings
===================
sh-4.2# gluster v get vol_9a7f161b2744bbd85b1b3c6b9fe50431 all | grep log
cluster.entry-change-log on
cluster.data-change-log on
cluster.metadata-change-log on
diagnostics.brick-log-level INFO
diagnostics.client-log-level INFO
diagnostics.brick-sys-log-level CRITICAL
diagnostics.client-sys-log-level CRITICAL
diagnostics.brick-logger (null)
diagnostics.client-logger (null)
diagnostics.brick-log-format (null)
diagnostics.client-log-format (null)
diagnostics.brick-log-buf-size 5
diagnostics.client-log-buf-size 5
diagnostics.brick-log-flush-timeout 120
diagnostics.client-log-flush-timeout 120
transport.listen-backlog 1024
debug.log-history no
debug.log-file no
changelog.changelog off
changelog.changelog-dir (null)
changelog.encoding ascii
changelog.rollover-time 15
changelog.fsync-interval 5
changelog.changelog-barrier-timeout 120
changelog.capture-del-path off
disperse.optimistic-change-log on
cluster.daemon-log-level INFO
sh-4.2#
sh-4.2# gluster v info vol_9a7f161b2744bbd85b1b3c6b9fe50431
Volume Name: vol_9a7f161b2744bbd85b1b3c6b9fe50431
Type: Replicate
Volume ID: 3d80645c-6b38-42da-b126-d9adcf4f1dc8
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: 10.70.46.127:/var/lib/heketi/mounts/vg_2360ce5871f583f999ce89909ed6e93e/brick_c69cb2b4a84462041700b3ecf5817d57/brick
Brick2: 10.70.46.132:/var/lib/heketi/mounts/vg_1d78c87af59224dc3db660bd1473eb95/brick_e1e7c55e641b50d2d178aa10711d7e09/brick
Brick3: 10.70.47.109:/var/lib/heketi/mounts/vg_087cd7144e81d5cd782829d58f5f2030/brick_82fb798427f57335f2784c14d2dc58fd/brick
Options Reconfigured:
cluster.choose-local: off
server.allow-insecure: on
user.cifs: off
features.shard-block-size: 64MB
features.shard: on
cluster.shd-wait-qlength: 10000
cluster.shd-max-threads: 8
cluster.locking-scheme: granular
cluster.data-self-heal-algorithm: full
cluster.quorum-type: auto
cluster.eager-lock: enable
network.remote-dio: disable
performance.strict-o-direct: on
performance.readdir-ahead: off
performance.open-behind: off
performance.stat-prefetch: off
performance.io-cache: off
performance.read-ahead: off
performance.quick-read: off
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off
cluster.brick-multiplex: on
sh-4.2#
Version-Release number of selected component (if applicable):
++++++++++++++++++++++++
sh-4.2# rpm -qa|grep tcmu-runner
tcmu-runner-1.2.0-23.el7rhgs.x86_64
sh-4.2#
sh-4.2# rpm -qa|grep gluster-block
gluster-block-0.2.1-24.el7rhgs.x86_64
sh-4.2# rpm -qa|grep config-shell
sh-4.2# rpm -qa|grep configshell
python-configshell-1.1.fb23-4.el7_5.noarch
sh-4.2# rpm -qa|grep rtslib
python-rtslib-2.1.fb63-12.el7_5.noarch
sh-4.2# rpm -qa|grep targetcli
targetcli-2.1.fb46-6.el7_5.noarch
sh-4.2#
How reproducible:
++++++++++++++++++++++++
Always
Steps to Reproduce:
++++++++++++++++++++++++
1. Check the volume status and brick PID
2. Kill the brick process and tcmu-runner will report the error message
3. Start the volume again, but no INFO logs are generated .
Actual results:
++++++++++++++++++++++++
tcmu-runner-glfs.log only logs E messages
Expected results:
++++++++++++++++++++++++
Add capability to include INFO (I) messages as well.
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-2018:2691