From 127f8adc86759af16097074d031d571e7a42667b Mon Sep 17 00:00:00 2001 From: cheese-cakee Date: Wed, 25 Mar 2026 04:14:16 +0530 Subject: [PATCH] rgw/logging: use trans_id for standard access log record In standard mode, the access log record was using s->req_id for the request ID field. The correct field is s->trans_id, which matches the x-amz-request-id returned in the S3 response. This is consistent with how all other RGW response code uses trans_id. Fixes: http://tracker.ceph.com/issues/75416 Signed-off-by: cheese-cakee --- src/rgw/rgw_bucket_logging.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/rgw/rgw_bucket_logging.cc b/src/rgw/rgw_bucket_logging.cc index bfb76a46c77..5d29e17ce21 100644 --- a/src/rgw/rgw_bucket_logging.cc +++ b/src/rgw/rgw_bucket_logging.cc @@ -585,7 +585,7 @@ int log_record(rgw::sal::Driver* driver, t, s->info.env->get("REMOTE_ADDR", "-"), dash_if_empty(user_or_account), - dash_if_empty(s->req_id), + dash_if_empty(s->trans_id), op_name, dash_if_empty_or_null(obj, obj->get_name()), s->info.method, -- 2.47.3