crimson/osd: inform in logs that TMAP is not supported

Simpler this way than to investigate for `EOPNOTSUPP`.

Signed-off-by: Radoslaw Zarzynski <rzarzyns@redhat.com>

diff --git a/src/crimson/osd/ops_executer.cc b/src/crimson/osd/ops_executer.cc
index 706105f091fddd683648298a5fde9ab7bc3600bf..ba2ece77bc507ee56ee3b239b4aeaad4ad1b8a93 100644 (file)
--- a/src/crimson/osd/ops_executer.cc
+++ b/src/crimson/osd/ops_executer.cc
@@ -591,6 +591,7 @@ OpsExecuter::do_execute_op(OSDOp& osd_op)
     // TODO: there was an effort to kill TMAP in ceph-osd. According to
     // @dzafman this isn't possible yet. Maybe it could be accomplished
     // before crimson's readiness and we'd luckily don't need to carry.
+    logger().info("crimson explicitly does not support CEPH_OSD_OP_TMAPUP");
     return dont_do_legacy_op();
 
   // OMAP