Actions
Bug #62013
closedObject with null version when using versioning and transition
% Done:
100%
Source:
Community (user)
Tags:
backport_processed
Backport:
pacific quincy reef
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Hi, I accidentally met this bug when trying to use transition on a bucket with versioning enabled. It will create 2 objects with the same key and null versionID
Steps to reproduce:
1. Create a bucket
2. Put an object
3. Enable bucket versioning
4. Add a lifecycle for transition to another storage class
5. After the lifecycle completed, we can see 2 objects with the same key and null versionID, like the following:
- mc ls dev/huybucket8 --versions
[2023-07-14 08:50:59 +07] 6B COLD null v2 PUT file1.text
[2023-07-14 08:50:59 +07] 6B COLD null v1 PUT file1.text
Bonus: If I also add a noncurrent expiration rule, the radosgw will repeatedly report this log
lifecycle: RGWLC::process() failed to acquire lock on lc.9, sleep 5, try again
lifecycle: RGWLC::process() failed to acquire lock on lc.8, sleep 5, try again
Actions