Description of problem: ====================== Raising a new bug for having an option to configure the location of tcmu-runner logs. As directed in https://bugzilla.redhat.com/show_bug.cgi?id=1477547#c19 Short summary: When we change /etc/sysconfig/gluster-blockd file and update the variable GB_LOGDIR to the new location, it is effective in logging only the gluster-block daemon logs at the new lcoation. Tcmu-runner logs continue to get appended to the older default location /var/log/gluster-block More information, context and logs present in BZ 1477547. Version-Release number of selected component (if applicable): ========================================================== tcmu-runner-1.2.0-12.el7rhgs.x86_64 gluster-block-0.2.1-8.el7rhgs.x86_64 glusterfs-3.8.4-42.el7rhgs.x86_64 How reproducible: ================ Always
Regarding option 2, I think we need a change in glusterd systemd file and its better to put it as $TCMU_LOGDIR instead of $GB_LOGDIR"
typo , /etc/systemd/gluster-blockd should be /etc/sysconfig/gluster-blockd
We have implemented a hack in CNS which should take care of this in CNS 3.6 release, so its not a blocker atm in RHGS.
There is already a way to tune logdir with tcmu-runner via cli with option --tcmu-log-dir. Looks like cns folks are already using it see comment 25. In upstream I have posted a patch for tweaking LOGDIR via Env variable too, but that is no more needed for now. Hence, Closing this bug as WORKS-FOR-ME, as there is no requirement for changes in tcmu-runner. Thanks!