Description of problem: Ran the test in a loop for 1 hour, couldn't recreate the failure. Removing the testcase from bad tests. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/13599 (Remove replace-brick-self-heal.t from bad-tests) posted (#1) for review on master by Anuradha Talur (atalur)
COMMIT: http://review.gluster.org/13599 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit e6a29ab2947eba3ee12ba3a94d4f04c41a22b5a4 Author: Anuradha Talur <atalur> Date: Fri Mar 4 01:41:09 2016 +0530 Remove replace-brick-self-heal.t from bad-tests Unable to recreate any failures even after running the test for more than an hour in a loop. Change-Id: Id1c7e60d39bce6b312dbb4ea0975079348bb1649 BUG: 1314549 Signed-off-by: Anuradha Talur <atalur> Reviewed-on: http://review.gluster.org/13599 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user