Bug 1102593 - Tests using cluser framework don't get their logs saved in the tar file
Summary: Tests using cluser framework don't get their logs saved in the tar file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-29 09:25 UTC by Avra Sengupta
Modified: 2014-11-11 08:33 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of:
Environment:
Last Closed: 2014-11-11 08:33:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Avra Sengupta 2014-05-29 09:25:06 UTC
Description of problem:
Tests using the cluster framework have their logs saved in /d/backends, which is not being saved in the compressed log file.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2014-05-29 09:35:06 UTC
REVIEW: http://review.gluster.org/7913 (DUMMY PATCH FOR FETCHING LOGS) posted (#3) for review on master by Avra Sengupta (asengupt)

Comment 2 Anand Avati 2014-05-29 09:35:12 UTC
REVIEW: http://review.gluster.org/7924 (tests/cluster.rc: Moving the glusterd logs for cluster testcases) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 3 Anand Avati 2014-05-29 17:50:54 UTC
COMMIT: http://review.gluster.org/7924 committed in master by Vijay Bellur (vbellur) 
------
commit a181282d1465c98c9b07bc7ea37e7096a7799a11
Author: Avra Sengupta <asengupt>
Date:   Thu May 29 06:53:32 2014 +0000

    tests/cluster.rc: Moving the glusterd logs for cluster testcases
    
    Moving the glusterd logs for cluster testcases from /d/backends to
    logdir.
    
    Change-Id: I6f22ca0c2faa87b0774e718c6c26d6547afd7c51
    BUG: 1102593
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/7924
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 4 Anand Avati 2014-05-30 02:59:08 UTC
REVIEW: http://review.gluster.org/7913 (DUMMY PATCH FOR FETCHING LOGS) posted (#4) for review on master by Avra Sengupta (asengupt)

Comment 5 Niels de Vos 2014-09-22 12:41:29 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 6 Niels de Vos 2014-11-11 08:33:44 UTC
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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


Note You need to log in before you can comment on or make changes to this bug.