Red Hat Bugzilla – Bug 1255599
Remove unwanted tests from volume-snapshot.t
Last modified: 2016-06-16 09:33:12 EDT
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):
Steps to Reproduce:
http://review.gluster.org/11972 posted for review
COMMIT: http://review.gluster.org/11972 committed in master by Raghavendra Talur (firstname.lastname@example.org)
Author: Atin Mukherjee <email@example.com>
Date: Fri Aug 21 10:54:39 2015 +0530
tests: remove unwanted tests from volume-snapshot.t
volume-snapshot.t failspuriously because of having additional test cases
which restarts glusterd and they are really not needed as far as the test
coverage is concerned. 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 all the peers are back to the cluster there could be a
case where any command which accesses the volume structure might end up in
corruption as volume handshaking is still in progress. This is because of volume
list is still not been made URCU protected.
Signed-off-by: Atin Mukherjee <firstname.lastname@example.org>
Reviewed-by: Avra Sengupta <email@example.com>
Reviewed-by: Raghavendra Talur <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.