Bug #47028: create a bucket with the same name as an existing bucket, but specify different ACL, rgw return "200 OK" - rgw - Ceph

Actions

Copy link

Bug #47028

closed

create a bucket with the same name as an existing bucket, but specify different ACL, rgw return "200 OK"

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

Status:

Resolved

Priority:

Normal

Assignee:

Target version:

% Done:

Source:

Tags:

backport_processed

Backport:

nautilus octopus

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

36978

Crash signature (v1):

Crash signature (v2):

Description

I try to create a bucket with the same name as an existing bucket, but specify different ACL, rgw return "200 OK". Run "rados_admin metadata get" to view the instance metadata object of the bucket, i found the bucket's ACL 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 open — 2 closed)

Actions

Copy link

Updated by Casey Bodley over 3 years ago

Status changed from New to Fix Under Review
Backport set to nautilus octopus

Actions

Copy link

Updated by Casey Bodley over 3 years ago

Pull request ID changed from 35170 to 36978

Actions

Copy link

Updated by Casey Bodley over 3 years ago

Status changed from Fix Under Review to Pending Backport

Actions

Copy link

Updated by Nathan Cutler over 3 years ago

Copied to Backport #47467: nautilus: create a bucket with the same name as an existing bucket, but specify different ACL, rgw return "200 OK" added

Actions

Copy link

Updated by Nathan Cutler over 3 years ago

Copied to Backport #47468: octopus: create a bucket with the same name as an existing bucket, but specify different ACL, rgw return "200 OK" added

Actions

Copy link