Bug #40806
multisite: radosgw-admin bucket sync status incorrectly reports "caught up" during full sync
% Done:
0%
Source:
Tags:
multisite
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
If no shards on incremental sync are behind, but some shards are still on full sync, the 'radosgw-admin bucket sync status' command should not report that the "bucket is caught up with source".
Related issues
History
#1 Updated by Casey Bodley over 1 year ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 29094
#2 Updated by Casey Bodley over 1 year ago
- Status changed from Fix Under Review to Pending Backport
#3 Updated by Casey Bodley over 1 year ago
- Status changed from Pending Backport to 7
#4 Updated by Casey Bodley over 1 year ago
- Status changed from 7 to Fix Under Review
#5 Updated by Casey Bodley over 1 year ago
- Status changed from Fix Under Review to Pending Backport
#6 Updated by Nathan Cutler over 1 year ago
- Copied to Backport #41492: luminous: multisite: radosgw-admin bucket sync status incorrectly reports "caught up" during full sync added
#7 Updated by Nathan Cutler over 1 year ago
- Copied to Backport #41493: nautilus: multisite: radosgw-admin bucket sync status incorrectly reports "caught up" during full sync added
#8 Updated by Nathan Cutler over 1 year ago
- Copied to Backport #41494: mimic: multisite: radosgw-admin bucket sync status incorrectly reports "caught up" during full sync added
#9 Updated by Nathan Cutler 3 months ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".