Closed brucen1030 closed 4 years ago
Describe the bug Multipart is not handled in DeleteBucket. The data will still reside in yig. And I think it will appear when user create a new bucket with the same name.
To Reproduce [root@localhost ~]# s3cmd listmp s3://zcc-test02/bigfile-multipart 18ef14d221c53c8ad2eba321a6ae579f17e1560ff0b8ba41 LastModified PartNumber ETag Size 2020-04-24T03:13:30.000Z 1 "abcf088715344654386548490bd96ee0" 5242880 ... [root@localhost ~]# s3cmd ls s3://zcc-test02 [root@localhost ~]# s3cmd rb s3://zcc-test02 Bucket 's3://zcc-test02/' removed
Expected behavior yig should remove the multiparts automatically like AWS S3.
Describe the bug
Multipart is not handled in DeleteBucket.
The data will still reside in yig.
And I think it will appear when user create a new bucket with the same name.
To Reproduce [root@localhost ~]# s3cmd listmp s3://zcc-test02/bigfile-multipart 18ef14d221c53c8ad2eba321a6ae579f17e1560ff0b8ba41 LastModified PartNumber ETag Size 2020-04-24T03:13:30.000Z 1 "abcf088715344654386548490bd96ee0" 5242880 ... [root@localhost ~]# s3cmd ls s3://zcc-test02 [root@localhost ~]# s3cmd rb s3://zcc-test02 Bucket 's3://zcc-test02/' removed
Expected behavior yig should remove the multiparts automatically like AWS S3.