Build cns-deploy-5.0.0-29.el7rhgs doesn't have tmcu-runner log path configurable.

Moving the bug to assigned.

with build cns-deploy-5.0.0-30.el7rhgs, the path to tcmu-runner logs seems to have a problem.

# ps -aux | grep tcmu-runner
root   3822  0.0  0.0 380904  4004 ?Ssl  09:38   0:00 /usr/bin/tcmu-runner --tcmu-log-dir=$TCMU_LOG_DIR
root   3986  0.0  0.0   9044   660 pts/1S+   09:43   0:00 grep tcmu-runner

sh-4.2# cat /usr/lib/systemd/system/tcmu-runner.service
[Unit]
Description=LIO Userspace-passthrough daemon
Requisite=glusterd.service
BindsTo=gluster-block-target.service
Before=gluster-block-target.service

[Service]
Type=dbus
BusName=org.kernel.TCMUService1
KillMode=process
EnvironmentFile=-/etc/sysconfig/tcmu-runner-params
ExecStart=/usr/bin/tcmu-runner --tcmu-log-dir=$TCMU_LOG_DIR


sh-4.2# cat  /etc/sysconfig/tcmu-runner-params
# tcmu log directory used by tcmu-runner
TCMU_LOG_DIR='/var/log/glusterfs/gluster-block'

sh-4.2# ls -l /$TCMU_LOG_DIR
total 28
-rw-r--r--. 1 root root 26554 Sep  5 16:41 gluster-block-cli.log
sh-4.2#
sh-4.2#
sh-4.2# ls -l /var/log/glusterfs/gluster-block
total 28
-rw-r--r--. 1 root root 26554 Sep  5 16:41 gluster-block-cli.log

Saravana & Talur figured out that the variable '$TCMU_LOG_DIR' is actually replaced by the path and hence the above behavior.

sh-4.2# ls -l /\$TCMU_LOG_DIR
total 4
-rw-------. 1 root root 1168 Sep  6 09:38 tcmu-runner.log

Moving the bug back to assigned to get this fixed.

This is fixed in latest image. cns-deploy > v31 has the fix.

tcmu-runner logs are again logged at /var/log/gluster-block directory

sh-4.2# ps -aux | grep 'tcmu'
root      2238  0.1  0.0 1539852 49092 ?       Ssl  10:16   0:21 /usr/bin/tcmu-runner --tcmu-log-dir=/var/log/gluster-block/
root     24455  0.0  0.0   9044   664 pts/0    S+   13:54   0:00 grep tcmu
sh-4.2# cat /usr/lib/systemd/system/tcmu-runner.service
[Unit]
Description=LIO Userspace-passthrough daemon
Requisite=glusterd.service
BindsTo=gluster-block-target.service
Before=gluster-block-target.service

[Service]
Type=dbus
BusName=org.kernel.TCMUService1
KillMode=process
EnvironmentFile=-/etc/sysconfig/tcmu-runner-params
ExecStart=/usr/bin/tcmu-runner --tcmu-log-dir=/var/log/gluster-block/
sh-4.2# cat  /etc/sysconfig/tcmu-runner-params
# tcmu log directory used by tcmu-runner
TCMU_LOGDIR='/var/log/glusterfs/gluster-block'
sh-4.2# ls -l /var/log/glusterfs/gluster-block
total 28
-rw-r--r--. 1 root root 26554 Sep  5 16:41 gluster-block-cli.log
sh-4.2# ls -l /var/log/gluster-block/
total 776
-rw-r--r--. 1 root root 505868 Sep 12 13:02 gluster-block-configshell.log
-rw-r--r--. 1 root root   4768 Sep 12 13:02 gluster-blockd.log
-rw-------. 1 root root 240379 Sep 12 13:56 tcmu-runner-glfs.log
-rw-------. 1 root root  16379 Sep 12 13:37 tcmu-runner.log

sed command error while updating parameter in tcmu-runner.service.

Following builds should fix this:

rhgs-server-docker-3.3.0-21
cns-deploy-5.0.0-38.el7rhgs

(In reply to Saravanakumar from comment #9)
> sed command error while updating parameter in tcmu-runner.service.
> 
> Following builds should fix this:
> 
> rhgs-server-docker-3.3.0-21
> cns-deploy-5.0.0-38.el7rhgs

Saravana, 

Please update the Fixed in Version as well.

(In reply to Prasanth from comment #10)
> (In reply to Saravanakumar from comment #9)
> > sed command error while updating parameter in tcmu-runner.service.
> > 
> > Following builds should fix this:
> > 
> > rhgs-server-docker-3.3.0-21
> > cns-deploy-5.0.0-38.el7rhgs
> 
> Saravana, 
> 
> Please update the Fixed in Version as well.

He has already mentioned it, so I am updating it.

verified in version cns-deploy-5.0.0-38.el7rhgs.x86_64

sh-4.2# ls -l /var/log/glusterfs/gluster-block/
total 228
-rw-r--r--. 1 root root  19170 Sep 14 14:01 gluster-block-cli.log
-rw-------. 1 root root 208729 Sep 14 14:01 tcmu-runner-glfs.log
-rw-------. 1 root root    357 Sep 14 12:31 tcmu-runner.log

tcmu runner logs are logged in /var/log/glusterfs/gluster-block directory. Moving the bug to verified.

doc text looks good to me

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:2877