From ecab9874d81d35baace484128234e0d0b51fc1dc Mon Sep 17 00:00:00 2001 From: Samuel Just Date: Wed, 8 May 2024 19:31:35 -0700 Subject: [PATCH] crimson/osd/pg: remove slightly confusing assert from PG::submit_transaction This assert should always hold, so it's not wrong. However, osd_op_p.at_version is chosen during transaction construction time using the current epoch via PG::get_next_version. Asserting it here is more confusing than helpful. Signed-off-by: Samuel Just (cherry picked from commit 7a04f6230d9376d155ac92a6c3bf1ab5eeca644f) --- src/crimson/osd/pg.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/src/crimson/osd/pg.cc b/src/crimson/osd/pg.cc index 457c98cf402..ad777c49d60 100644 --- a/src/crimson/osd/pg.cc +++ b/src/crimson/osd/pg.cc @@ -813,7 +813,6 @@ PG::submit_transaction( } epoch_t map_epoch = get_osdmap_epoch(); - ceph_assert(!has_reset_since(osd_op_p.at_version.epoch)); peering_state.pre_submit_op(obc->obs.oi.soid, log_entries, osd_op_p.at_version); peering_state.update_trim_to(); -- 2.39.5