Project

General

Profile

Bug #38420

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

Added by Abhishek Lekshmanan about 5 years ago. Updated almost 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

Duplicated by rgw - Bug #39622: rgw:RGWGetBucketVersioning on non-existing bucket does not return NoSuchBucket (http=404) Duplicate 05/08/2019
Duplicated by rgw - Bug #50107: rgw:throw error NoSuchBucket when bucket not exists(nautilus) Duplicate
Copied to rgw - Backport #39696: luminous: rgw: success returned for put bucket versioning on a non existant bucket Resolved
Copied to rgw - Backport #39697: mimic: rgw: success returned for put bucket versioning on a non existant bucket Resolved
Copied to rgw - Backport #50233: nautilus: rgw: success returned for put bucket versioning on a non existant bucket Resolved

History

#1 Updated by Abhishek Lekshmanan about 5 years ago

  • Status changed from New to 17

#2 Updated by Abhishek Lekshmanan about 5 years ago

  • Assignee set to Abhishek Lekshmanan

#3 Updated by Abhishek Lekshmanan about 5 years ago

  • Status changed from 17 to Resolved

#4 Updated by Abhishek Lekshmanan almost 5 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to luminous, mimic

#5 Updated by Casey Bodley almost 5 years ago

  • Duplicated by Bug #39622: rgw:RGWGetBucketVersioning on non-existing bucket does not return NoSuchBucket (http=404) added

#6 Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #39696: luminous: rgw: success returned for put bucket versioning on a non existant bucket added

#7 Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #39697: mimic: rgw: success returned for put bucket versioning on a non existant bucket added

#8 Updated by Nathan Cutler over 4 years ago

  • Pull request ID set to 26569

#9 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".

#10 Updated by Nathan Cutler almost 3 years ago

  • Status changed from Resolved to Pending Backport
  • Backport changed from luminous, mimic to luminous, mimic, nautilus

#11 Updated by Nathan Cutler almost 3 years ago

  • Copied to Backport #50233: nautilus: rgw: success returned for put bucket versioning on a non existant bucket added

#12 Updated by Nathan Cutler almost 3 years ago

  • Duplicated by Bug #50107: rgw:throw error NoSuchBucket when bucket not exists(nautilus) added

#13 Updated by Loïc Dachary almost 3 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".

Also available in: Atom PDF