Bug #39635
closedmultisite: mismatch of bucket creation times from List Buckets
0%
Description
Reproduces with two zones. s3cmd config c1.s3cfg points to the master zone, and c2.s3cfg points to the secondary zone.
1. Create a bucket on the master zone, verify that it syncs with the same creation time:
$ s3cmd -c c1.s3cfg mb s3://bucket
Bucket 's3://bucket/' created
$ s3cmd -c c1.s3cfg ls
2019-05-08 17:33 s3://bucket
$ s3cmd -c c2.s3cfg ls
2019-05-08 17:33 s3://bucket
2. Stop the secondary zone's gateway(s) and wait a couple minutes so you can tell whether the creation time changes.
3. Delete and recreate the bucket on the master zone.
$ s3cmd -c c1.s3cfg rb s3://bucket
Bucket 's3://bucket/' removed
$ s3cmd -c c1.s3cfg mb s3://bucket
Bucket 's3://bucket/' created
4. Restart secondary zone's gateways(s) so they sync the new bucket without the deletion in between.
5. Wait for metadata sync to catch up, then check the creation times again:
$ s3cmd -c c1.s3cfg ls
2019-05-08 17:37 s3://bucket
$ s3cmd -c c2.s3cfg ls
2019-05-08 17:33 s3://bucket
Updated by Casey Bodley almost 5 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 28045
Updated by Casey Bodley almost 5 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #39733: luminous: multisite: mismatch of bucket creation times from List Buckets added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #39734: mimic: multisite: mismatch of bucket creation times from List Buckets added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #39735: nautilus: multisite: mismatch of bucket creation times from List Buckets added
Updated by Nathan Cutler over 4 years 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".