Project

General

Profile

Actions

Bug #47027

closed

create a bucket with the same name as an existing bucket in anthor zonegroup return 200

Added by lei cao over 3 years ago. Updated over 1 year ago.

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

0%

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

Description

In slave zonegroup, i try to create a bucket with the same name as an existing bucket in master zonegroup, and specify slave zonegroup in LocationConstraint element of XML body, rgw return "200 OK". Run "rados_admin metadata get" to view the instance metadata object of the bucket, i found the bucket's zonegreoup has not changed. It really should n’t change. But, it's not appropriate to return 200. Similar to specifying a different placemen when creating an existing bucket, rgw should return "409 Conflict" in this scenario.


Related issues 2 (0 open2 closed)

Copied to rgw - Backport #47469: nautilus: create a bucket with the same name as an existing bucket in anthor zonegroup return 200RejectedActions
Copied to rgw - Backport #47470: octopus: create a bucket with the same name as an existing bucket in anthor zonegroup return 200RejectedCasey BodleyActions
Actions #1

Updated by Casey Bodley over 3 years ago

  • Status changed from New to Fix Under Review
  • Backport set to nautilus octopus
Actions #2

Updated by Casey Bodley over 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #3

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47469: nautilus: create a bucket with the same name as an existing bucket in anthor zonegroup return 200 added
Actions #4

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47470: octopus: create a bucket with the same name as an existing bucket in anthor zonegroup return 200 added
Actions #5

Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed
Actions #6

Updated by Konstantin Shalygin over 1 year ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF