Bug #47529
openIn multi-site and versioned scenarios, operations with null versionId cannot be deleted synchronously
0%
Description
1.first,complete the multisite configuration, rgw1 in master zone, rgw2 in secondary zone.
2.create a bucket named bk01 in the master zone.
3.upload an object with key aa to bk01.
4.enable bk01 version, eg: aws s3api put-bucket-versioning --versioning-configuration Status=Enabled --endpoint=http://rgw1:9000 --bucket bk01.
5.upload an object with key aa to bk01 again.
6.delete version id is null obj in master zone, eg: aws s3api delete-object --endpoint=http://rgw1:9000 --bucket bk01 --key aa --version-id null
7.view in master zone: aws s3api list-object-versions --endpoint=http://rgw1:9000 --bucket bk01
{
"Versions": [
{
"LastModified": "2020-09-18T05:59:55.691Z",
"VersionId": "67bzuCK-i73JVtPsn0U8hjPHfwgqnD3",
"ETag": "\"f86cb82ff889919256be6f2911c31eb8\"",
"StorageClass": "STANDARD",
"Key": "aa",
"Owner": {
"DisplayName": "dyp01",
"ID": "dyp01"
},
"IsLatest": true,
"Size": 1276
}
]
}
8.view in secondary zone: aws s3api list-object-versions --endpoint=http://rgw2:9000 --bucket bk01
{
"Versions": [
{
"LastModified": "2020-09-18T05:59:55.691Z",
"VersionId": "67bzuCK-i73JVtPsn0U8hjPHfwgqnD3",
"ETag": "\"f86cb82ff889919256be6f2911c31eb8\"",
"StorageClass": "STANDARD",
"Key": "aa",
"Owner": {
"DisplayName": "dyp01",
"ID": "dyp01"
},
"IsLatest": true,
"Size": 1276
},
{
"LastModified": "2020-09-18T05:59:32.306Z",
"VersionId": "null",
"ETag": "\"f86cb82ff889919256be6f2911c31eb8\"",
"StorageClass": "STANDARD",
"Key": "aa",
"Owner": {
"DisplayName": "dyp01",
"ID": "dyp01"
},
"IsLatest": false,
"Size": 1276
}
]
}
However, their output should be consistent.