Red Hat Bugzilla – Bug 1313775
ec-read-policy.t can report a false-failure
Last modified: 2016-06-16 09:59:06 EDT
Description of problem:
One of the tests in ec-read-policy.t checks for READ operations in all bricks using the output of a 'gluster volume profile' command and couting lines containing "READ". This can fail if, for some reason, one or more bricks has also executed a READDIR fop.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/13575 (tests: Fix spurious failure of ec-read-policy.t) posted (#1) for review on master by Xavier Hernandez (email@example.com)
REVIEW: http://review.gluster.org/13575 (tests: Fix spurious failure of ec-read-policy.t) posted (#2) for review on master by Raghavendra Talur (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/13575 committed in master by Jeff Darcy (email@example.com)
Author: Xavier Hernandez <firstname.lastname@example.org>
Date: Wed Mar 2 11:35:44 2016 +0100
tests: Fix spurious failure of ec-read-policy.t
Signed-off-by: Xavier Hernandez <email@example.com>
Tested-by: Raghavendra Talur <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
Reviewed-by: Jeff Darcy <firstname.lastname@example.org>
"tests" component is for tests framework only.
File a bug under test component if you find a bug in
1. any of the *.rc files under tests/
For everything else, the bug should be filed on
1. component which is being tested by .t file if the .t file requires fix.
2. component which is causing a valid .t file to fail in regression.
I have used my best judgement here to move the bug to right component.
In case of ambiguity, I have placed the blame on the .t file component.
Please consider test bugs under the same backlog list that tracks other bugs in your component.
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.