Bug #58822
closedrgw/syncpolicy: Unable to restrict sync to subset of zones
0%
Description
Suppose there are three zones (zg1-1, zg1-2, zg1-3) in a zonegroup, out of which sync policy is created to allow sync between only zg1-1, zg1-2 as shown below -
#radosgw-admin sync info --group-id=zg1-policy1
{
"sources": [
{
"id": "zg1-pipe",
"source": {
"zone": "zg1-2",
"bucket": "*"
},
"dest": {
"zone": "zg1-1",
"bucket": "*"
},
"params": {
"source": {
"filter": {
"tags": []
}
},
"dest": {},
"priority": 0,
"mode": "system",
"user": ""
}
}
],
"dests": [
{
"id": "zg1-pipe",
"source": {
"zone": "zg1-1",
"bucket": "*"
},
"dest": {
"zone": "zg1-2",
"bucket": "*"
},
"params": {
"source": {
"filter": {
"tags": []
}
},
"dest": {},
"priority": 0,
"mode": "system",
"user": ""
}
}
],
Expected behavior- is that objects created in zg1-1, zg1-2 will synced among each other but will not be replicated to zg1-3. However that doesn't seem to be the case.
Observations: Objects created in zg1-1, zg1-2 are being copied to zg1-3 even though there is no policy configured allowing the same. Strangely, the objects created at zg1-3 are not being replicated to zg1-1 or zg1-2.
Updated by Casey Bodley about 1 year ago
- Tags changed from rgw, to multisite sync-policy
Updated by Soumya Koduri about 1 year ago
- Pull request ID set to 50397
This seem to have caused due to incorrect zone configuration. Due to a bug in test-rgw-multisite.sh, the endpoints created for zone2 are being added to zone3 as well resulting in zonegroup update issues for zone3.
Updated by Soumya Koduri about 1 year ago
- Status changed from New to Resolved
- Backport set to reef