From a02f2510fcc800b9f2cf2a06401a7b97d5985409 Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Fri, 5 Jul 2013 16:03:49 -0700 Subject: [PATCH] mon: remove bad assert about monmap version It is possible to start a sync when our newest monmap is 0. Usually we see e0 from probe, but that isn't always published as part of the very first paxos transaction due to the way PaxosService::_active generates it's first initial commit. In any case, having e0 here is harmless. Fixes: #5509 Signed-off-by: Sage Weil Reviewed-by: Joao Eduardo Luis (cherry picked from commit 85a1d6cc5d3852c94d1287b566656c5b5024fa13) --- src/mon/Monitor.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/src/mon/Monitor.cc b/src/mon/Monitor.cc index 42fc15c5905bf..9d436f1e56905 100644 --- a/src/mon/Monitor.cc +++ b/src/mon/Monitor.cc @@ -1384,7 +1384,6 @@ void Monitor::sync_obtain_latest_monmap(bufferlist &bl) if (monmap->epoch > latest_monmap.epoch) latest_monmap = *monmap; - assert(latest_monmap.epoch > 0); dout(1) << __func__ << " obtained monmap e" << latest_monmap.epoch << dendl; latest_monmap.encode(bl, CEPH_FEATURES_ALL); -- 2.39.5