From 6295578f165db7e07e2c205aebb19aa00b184844 Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Sat, 25 Feb 2012 21:35:31 -0800 Subject: [PATCH] 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. --- suites/regression/singleton/all/lost-unfound.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/suites/regression/singleton/all/lost-unfound.yaml b/suites/regression/singleton/all/lost-unfound.yaml index 21d1a05ac4f..ece6ceb2ea3 100644 --- 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: