Description of problem: Separate cli log files are not maintained for cluster regression tests resulting in pain for debugging issues Version-Release number of selected component (if applicable): Mainline How reproducible: Always Steps to Reproduce: 1.Run any cluster regression test (For eg : mgmt_v3_locks.t) Actual results: Only cli.log file is created although there are more than one cli instances executed. Expected results: cli log file is expected per cli instance.
REVIEW: http://review.gluster.org/9100 (cli : Maintain separate cli log file per cli instance for cluster regression tests) posted (#1) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/9100 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 7c9e95f1876ca0d209509358e6d4e58c910dd71e Author: Atin Mukherjee <amukherj> Date: Wed Nov 12 12:15:11 2014 +0530 cli : Maintain separate cli log file per cli instance for cluster regression tests Change-Id: I7f49f4999d997b99c103fd67d13f972937e3aa92 BUG: 1162987 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/9100 Reviewed-by: Kaushal M <kaushal> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
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-3.7.0, please open a new bug report. glusterfs-3.7.0 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] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user