+++ This bug was initially created as a clone of Bug #1145189 +++ Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Anand Avati on 2014-09-22 10:13:41 EDT --- REVIEW: http://review.gluster.org/8809 (test : Fix for spurious failure) posted (#1) for review on release-3.6 by Sachin Pandit (spandit) --- Additional comment from Anand Avati on 2014-09-23 02:21:43 EDT --- REVIEW: http://review.gluster.org/8809 (test : Fix for spurious failure) posted (#2) for review on release-3.6 by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/8814 (test : Fix for spurious failure) posted (#1) for review on master by Sachin Pandit (spandit)
Problem : Once the features.uss is enabled it does not wait for the process to be created. And if we try to check for the pid of the snapd then it will not be present which causes a failure.
REVIEW: http://review.gluster.org/8814 (test : Fix for spurious failure) posted (#2) for review on master by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/8814 (test : Fix for spurious failure) posted (#3) for review on master by Sachin Pandit (spandit)
COMMIT: http://review.gluster.org/8814 committed in master by Vijay Bellur (vbellur) ------ commit 933e5bd5a7b32394c7a3c6e84543dc48ed24a732 Author: Sachin Pandit <spandit> Date: Tue Sep 23 04:53:47 2014 +0530 test : Fix for spurious failure Problem : Once the features.uss is enabled it does not wait for the process to be created. And if we try to check for the pid of the snapd then it will not be present which causes a failure. Solution : Adding a EXPECT_WITHIN which waits to get the pid until certain time period. Change-Id: If075860173a996f9eee13b346e939686b94ec3f6 BUG: 1145450 Signed-off-by: Sachin Pandit <spandit> Reviewed-on: http://review.gluster.org/8814 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu> Reviewed-by: Vijay Bellur <vbellur>
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