lost_unfound: do peer after, until wait_for_clean propagates last_epoch_started

The peer task does wait_for_clean, and then lost_unfound immediately marks
something down.  But the PGs become clean before the replica last_epoch_started
is moved forward in time, which means they block waiting for the now down
OSD.  Needlessly.

Until we fix this, just do the peer test after.

diff --git a/suites/regression/singleton/all/lost-unfound.yaml b/suites/regression/singleton/all/lost-unfound.yaml
index 21d1a05ac4f02bdd354a479d0352f07a17d3f818..ece6ceb2ea35754f3eb126cc5c9721423c833d5f 100644 (file)
--- a/suites/regression/singleton/all/lost-unfound.yaml
+++ b/suites/regression/singleton/all/lost-unfound.yaml
@@ -10,5 +10,5 @@ tasks:
 - ceph:
     log-whitelist:
     - objects unfound and apparently lost
-- peer:
 - lost_unfound:
+- peer: