Description of problem: When run on the master zone, `radosgw-admin sync status` will list the datalog shards that are behind, but does not display the line "oldest incremental change not applied: 2019-03-25 16:28:23.0.977968s". This makes it difficult to tell whether data sync is making progress. Version-Release number of selected component (if applicable): How reproducible: Always reproducible when run on the master zone of the master zonegroup Steps to Reproduce: 1. Configure a multisite setup with two zones. 2. Create a bucket on the master zone and upload an object. 3. Wait for the secondary zone to sync both. 4. Stop the master zone gateway(s). 5. Upload some more objects to that bucket on the secondary zone. 6. Observe the sync status on the master zone: $ radosgw-admin sync status Actual results: data sync source: 216c57d2-e8c8-40b7-bb5d-c34aecf1b962 (a2) syncing full sync: 0/128 shards incremental sync: 128/128 shards data is behind on 1 shards behind shards: [6] Expected results: data sync source: 216c57d2-e8c8-40b7-bb5d-c34aecf1b962 (a2) syncing full sync: 0/128 shards incremental sync: 128/128 shards data is behind on 1 shards behind shards: [6] oldest incremental change not applied: 2019-03-25 16:28:23.0.977968s Additional info:
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, 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-2019:0911
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days