crimson/osd: objects without omap header may not necessarily be a error

There are circumstances in which objects don't have omap headers, so this should
not be treated as an error

Signed-off-by: Xuehan Xu <xxhdx1985126@gmail.com>

diff --git a/src/crimson/osd/replicated_recovery_backend.cc b/src/crimson/osd/replicated_recovery_backend.cc
index 70c268e83aff1c9dfa0c2e7b0788d6e14e18f424..218550fa73219fe5c39aaaf450bf20d028241384 100644 (file)
--- a/src/crimson/osd/replicated_recovery_backend.cc
+++ b/src/crimson/osd/replicated_recovery_backend.cc
@@ -432,8 +432,7 @@ ReplicatedRecoveryBackend::read_metadata_for_push_op(
       }))
   ).then_unpack([&new_progress, push_op](auto bl, auto attrs) {
     if (bl.length() == 0) {
-      logger().error("read_metadata_for_push_op: fail to read omap header");
-      return eversion_t{};
+      logger().warn("read_metadata_for_push_op: fail to read omap header");
     } else if (attrs.empty()) {
       logger().error("read_metadata_for_push_op: fail to read attrs");
       return eversion_t{};