Project

General

Profile

Actions

Bug #38420

closed

rgw: success returned for put bucket versioning on a non existant bucket

Added by Abhishek Lekshmanan about 5 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
luminous, mimic, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

$ aws s3api list-buckets --endpoint=http://localhost:8000

{
    "Owner": {
        "DisplayName": "tester1",
        "ID": "s3test1" 
    },
    "Buckets": []
}

(aws) [abhishekl@d18:~/spells/pyspells/s3]$
aws s3api put-bucket-versioning --bucket bucket1 --versioning-configuration Status=Enabled --endpoint=http://localhost:8000
(aws) [abhishekl@d18:~/spells/pyspells/s3]$
aws s3api list-buckets --endpoint=http://localhost:8000

{
    "Owner": {
        "DisplayName": "tester1",
        "ID": "s3test1" 
    },
    "Buckets": []
}

We also unfortunately create a bucket instance in the cluster which shouldn't happen


Related issues 5 (0 open5 closed)

Has duplicate rgw - Bug #39622: rgw:RGWGetBucketVersioning on non-existing bucket does not return NoSuchBucket (http=404)Duplicate05/08/2019

Actions
Has duplicate rgw - Bug #50107: rgw:throw error NoSuchBucket when bucket not exists(nautilus)Duplicate

Actions
Copied to rgw - Backport #39696: luminous: rgw: success returned for put bucket versioning on a non existant bucketResolvedNathan CutlerActions
Copied to rgw - Backport #39697: mimic: rgw: success returned for put bucket versioning on a non existant bucketResolvedPrashant DActions
Copied to rgw - Backport #50233: nautilus: rgw: success returned for put bucket versioning on a non existant bucketResolvedNathan CutlerActions
Actions

Also available in: Atom PDF