Previously, calling mds_stop without mds_fail meant
that if the filesystem creation was not quick, then
we would see those daemons go laggy. This starts
to trigger failures now that we have cluster log
messages that fire when a daemon gets failed out
due to being laggy.
Signed-off-by: John Spray <john.spray@redhat.com>
# To avoid any issues with e.g. unlink bugs, we destroy and recreate
# the filesystem rather than just doing a rm -rf of files
self.mds_cluster.mds_stop()
+ self.mds_cluster.mds_fail()
self.mds_cluster.delete_all_filesystems()
self.fs = None # is now invalid!