Merge pull request #20292 from smithfarm/wip-22018-jewel

jewel: rgw: segmentation fault when starting radosgw after reverting .rgw.root

Reviewed-by: Orit Wasserman <owasserm@redhat.com>

diff --cc src/rgw/rgw_rados.cc
index a01068e7c5089f9183c3e02128c86a00e2ff2f4c,0ffe5e082a3090a68d866b50c9670ae40139590e..6f9ba79250d6b3bd106f3dc614726bcc5f3b3231
--- 1/src/rgw/rgw_rados.cc
--- 2/src/rgw/rgw_rados.cc
+++ b/src/rgw/rgw_rados.cc
@@@ -3967,17 -3900,9 +3967,10 @@@ int RGWRados::init_complete(
      obj_expirer->start_processor();
    }
  
-   if (run_sync_thread) {
-     // initialize the log period history. we want to do this any time we're not
-     // running under radosgw-admin, so we check run_sync_thread here before
-     // disabling it based on the zone/zonegroup setup
-     meta_mgr->init_oldest_log_period();
-   }
- 
    /* no point of running sync thread if we don't have a master zone configured
       or there is no rest_master_conn */
 -  if (get_zonegroup().master_zone.empty() || !rest_master_conn) {
 +  if (get_zonegroup().master_zone.empty() || !rest_master_conn
 +      || current_period.get_id().empty()) {
      run_sync_thread = false;
    }