Bug 2317969

Summary: [rfe][replication-header]: ReplicationStatus shows as 'PENDING' even when the object has synced to the other zone.
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vidushi Mishra <vimishra>
Component: RGW-MultisiteAssignee: Casey Bodley <cbodley>
Status: CLOSED ERRATA QA Contact: Vidushi Mishra <vimishra>
Severity: high Docs Contact: Rivka Pollack <rpollack>
Priority: unspecified    
Version: 8.0CC: cbodley, ceph-eng-bugs, cephqe-warriors, mbenjamin, rpollack, tserlin
Target Milestone: ---Keywords: FutureFeature
Target Release: 8.1Flags: mbenjamin: needinfo? (cbodley)
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-19.2.1-112.el9cp Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-06-26 12:17:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vidushi Mishra 2024-10-11 06:28:46 UTC
Description of problem:


After uploading an object in a multisite , we see the source zone reports the "ReplicationStatus" in PENDING state via the radosgw-admin object stat and head-object s3api even though the object has synced to the destination zone where the "ReplicationStatus" shows as "REPLICA"

Version-Release number of selected component (if applicable):

ceph version 19.2.0-12.el9cp 

How reproducible:

3/3

Steps to Reproduce:
1. create a bucket on the source zone "test3" and upload an object "file"
2. let the object sync to the destination zone and wait for a few mins (more than 20mins)


Actual results:

We observe that the object REPLICATION STATUS on the source zone is always in PENDING state obtained via the radosgw-admin object stat or s3api head-object even when the object has synced to the destination zone.

Expected results:

ReplicationStatus on the source zone for an object should be COMPLETED if it has successfully synced to the destination.

Additional info:

Comment 14 errata-xmlrpc 2025-06-26 12:17:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat Ceph Storage 8.1 security, bug fix, and enhancement updates), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2025:9775