+++ This bug was initially created as a clone of Bug #1255599 +++ Description of problem: volume-snapshot.t is failing spuriously because of having additional test cases which restarts glusterd. Currently glusterd doesn't have a mechanism to indicate that volumes handshaking has been completed or not, due to this even if the peer handshaking finishes and triggering a volume based command might end up in a corruption as volume handshaking is still in progress. Version-Release number of selected component (if applicable): mainline How reproducible: intermittent Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Atin Mukherjee on 2015-08-21 01:53:13 EDT --- http://review.gluster.org/11972 posted for review
REVIEW: http://review.gluster.org/11975 (tests: remove unwanted tests from volume-snapshot.t) posted (#1) for review on release-3.7 by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/11975 (tests: remove unwanted tests from volume-snapshot.t) posted (#2) for review on release-3.7 by Raghavendra Talur (rtalur)
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.4, please open a new bug report. glusterfs-3.7.4 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/12496 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user