Actions
Bug #22416
closeds3cmd move object error
% Done:
0%
Source:
other
Tags:
Backport:
jewel luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Hi, I'm using s3cmd to test Ceph RGW, and I found a bug when I tried to rename an object inside a bucket:
root / $ s3cmd ls s3://bucket1
2017-12-13 04:04 1871 s3://bucket1/obj1
2017-12-13 04:04 8034 s3://bucket1/obj2
root / $ s3cmd mv s3://bucket1/obj1 s3://bucket1/obj3
move: 's3://bucket1/obj1' -> 's3://bucket1/obj3'
root / $ s3cmd ls s3://bucket1
2017-12-13 04:04 1871 s3://bucket1/obj1
2017-12-13 04:04 8034 s3://bucket1/obj2
2017-12-13 07:06 1871 s3://bucket1/obj3
The source object still exists even though obj3 has been created.
Updated by Tao CHEN over 6 years ago
Knowning that this bug doesn't show with AWS S3.
Updated by Enming Zhang over 6 years ago
Updated by John Spray over 6 years ago
- Project changed from Ceph to rgw
- Category deleted (
22)
Updated by Casey Bodley over 6 years ago
- Status changed from New to 7
- Backport set to jewel luminous
Updated by Yuri Weinstein over 6 years ago
Updated by Matt Benjamin over 6 years ago
- Status changed from 7 to Pending Backport
Updated by Nathan Cutler over 6 years ago
- Copied to Backport #22635: luminous: s3cmd move object error added
Updated by Nathan Cutler over 6 years ago
- Copied to Backport #22636: jewel: s3cmd move object error added
Updated by Nathan Cutler about 6 years ago
- Status changed from Pending Backport to Resolved
Actions