Hi all, I’m following up on my earlier email regarding RGW multisite replication behavior in Ceph 19.2.3. To briefly recap: replication works as expected for buckets owned by regular users, but for buckets owned by the RGW Account (for example, RGW84754594545284760), object replication remains in a PENDING state indefinitely. There are no errors reported in the sync status on either zone. I wanted to check if anyone else has encountered a similar issue with account-owned buckets in multisite setups, or if this is a known limitation or bug in Quincy. Any insights, confirmations, or suggested workarounds would be greatly appreciated. Thanks in advance for your time and help. Best regards, Ashok ---- On Tue, 04 Nov 2025 15:19:23 +0530 Ashok Kumar M <ashok.m@zybisys.com> wrote --- Hi, I’m currently using Ceph version 19.2.3 and have a setup with two zones (zone-a and zone-b) under a single zonegroup (zonegroup-a) and realm (realm-a). When I replicate objects from bucket-a (in zone-a) to bucket-b (in zone-b) for buckets owned by a regular user (ex: my-user), the replication works successfully. However, replication does not work for buckets owned by the RGW Account (ex: RGW84754594545284760). In this case: There are no errors shown in the sync status on either zone. The replication status of the objects in the source bucket remains in a “PENDING” state indefinitely. Has anyone else encountered a similar issue, or is there any known workaround for this? I would really appreciate any kind of advice or guidance regarding this. Thanks, Ashok M Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."