From 59f73a5aafd1d3ded4f64800541ff43ee7974aba Mon Sep 17 00:00:00 2001
From: "Adam C. Emerson" <aemerson@redhat.com>
Date: Thu, 10 Apr 2025 12:06:21 -0400
Subject: [PATCH] rgw: Don't print spurious error on `radosgw-admin` exit

When debugging crashes related to `RGWDataChangesLog` shutdown, I
fixed the crashes, but broke the logic that decides whether to print
the error.

Fixes: https://tracker.ceph.com/issues/70864
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
---
 src/rgw/driver/rados/rgw_datalog.cc | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/rgw/driver/rados/rgw_datalog.cc b/src/rgw/driver/rados/rgw_datalog.cc
index 43843063464..d6ed19f20b4 100644
--- a/src/rgw/driver/rados/rgw_datalog.cc
+++ b/src/rgw/driver/rados/rgw_datalog.cc
@@ -1357,10 +1357,13 @@ bool RGWDataChangesLog::going_down() const
 
 asio::awaitable<void> RGWDataChangesLog::shutdown() {
   DoutPrefix dp{cct, ceph_subsys_rgw, "Datalog Shutdown"};
-  if (down_flag || !ran_background) {
+  if (down_flag) {
     co_return;
   }
   down_flag = true;
+  if (!ran_background)  {
+    co_return;
+  }
   renew_stop();
   // Revisit this later
   if (renew_signal)
-- 
2.47.3