Actions
Bug #39629
closedmultisite: DELETE Bucket CORS is not forwarded to master zone
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
easy first bug
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
PUT Bucket CORS does forward, but DELETE does not
Updated by Casey Bodley almost 5 years ago
- Related to Bug #16888: [multisite] operating bucket's acl&cors is not restricted on slave zone added
Updated by Casey Bodley almost 5 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 28276
Updated by Casey Bodley almost 5 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40513: luminous: multisite: DELETE Bucket CORS is not forwarded to master zone added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40514: mimic: multisite: DELETE Bucket CORS is not forwarded to master zone added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40515: nautilus: multisite: DELETE Bucket CORS is not forwarded to master zone added
Updated by Nathan Cutler about 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".
Actions