Description of problem: https://build.gluster.org/job/regression-test-with-multiplex/60/console 02:43:26 [21:13:26] Running tests in file ./tests/basic/ec/ec-data-heal.t 02:48:01 cat: /proc/16293/cmdline: No such file or directory 02:48:01 Usage: gf_attach uds_path volfile_path (to attach) 02:48:01 gf_attach -d uds_path brick_path (to detach) 02:49:00 rm: cannot remove `/mnt/glusterfs/0/xy_zzy': Transport endpoint is not connected 02:49:20 md5sum: /mnt/glusterfs/0/file: Transport endpoint is not connected 02:50:01 rm: cannot remove `/mnt/glusterfs/0/xy_zzy': Transport endpoint is not connected 02:50:21 md5sum: /mnt/glusterfs/0/file: Transport endpoint is not connected 02:50:42 ./tests/basic/ec/ec-data-heal.t .. 02:50:42 1..33 02:50:42 ok 1, LINENUM:9 02:50:42 ok 2, LINENUM:10 02:50:42 ok 3, LINENUM:11 02:50:42 ok 4, LINENUM:12 02:50:42 ok 5, LINENUM:14 02:50:42 ok 6, LINENUM:15 02:50:42 ok 7, LINENUM:18 02:50:42 ok 8, LINENUM:28 02:50:42 ok 9, LINENUM:29 02:50:42 not ok 10 , LINENUM:32 02:50:42 FAILED COMMAND: eval /build/install/sbin/glusterfsd -s slave26.cloud.gluster.org --volfile-id patchy.slave26.cloud.gluster.org.d-backends-patchy0 -p /var/lib/glusterd/vols/patchy/run/slave26.cloud.gluster.org-d-backends-patchy0.pid -S /var/run/gluster/979cf846da8c63118aaae8125b1e5887.socket --brick-name /d/backends/patchy0 -l /var/log/glusterfs/bricks/d-backends-patchy0.log --xlator-option *-posix.glusterd-uuid=36eb0fe1-6f16-40dd-a011-b30dd354a65f --brick-port 49152 --xlator-option patchy-server.listen-port=49152 02:50:42 not ok 11 Got "2" instead of "^0$", LINENUM:34 02:50:42 FAILED COMMAND: ^0$ get_pending_heal_count patchy 02:50:42 not ok 12 Got "2" instead of "^0$", LINENUM:36 02:50:42 FAILED COMMAND: ^0$ get_pending_heal_count patchy 02:50:42 ok 13, LINENUM:45 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/17508 (ec: fix ec-data-heal.t failure) posted (#1) for review on master by Atin Mukherjee (amukherj)
REVIEW: https://review.gluster.org/17508 (ec: fix ec-data-heal.t failure) posted (#2) for review on master by Ashish Pandey (aspandey)
COMMIT: https://review.gluster.org/17508 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 05b2fbd077cadc409994762e346ef94f4904545b Author: Atin Mukherjee <amukherj> Date: Mon Jun 12 15:09:10 2017 +0530 ec: fix ec-data-heal.t failure With brick mux enabled, this test was constantly failing. Further it was found that the the test does a series of killing a particular brick and bringing it up in cmdline where as just starting the volume with force would suffice. Change-Id: Iee491d0777eaa28dca5c78f92d4b400fcc897fd2 BUG: 1460638 Signed-off-by: Atin Mukherjee <amukherj> Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: https://review.gluster.org/17508 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu> CentOS-regression: Gluster Build System <jenkins.org>
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.12.0, please open a new bug report. glusterfs-3.12.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://lists.gluster.org/pipermail/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/