Actions
Feature #1027
closedrgw log operations on non-existent bucket
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
When logging an operation on non-existent bucket we should append the log on a special log object and not create an object for that bucket. We should make it also configurable so that we can either disable logging such anonymous operations or any operations.
Updated by Yehuda Sadeh almost 13 years ago
Starting at commit:8836b8447a3a70fc6dd647d070d763f283084ee7 we don't log operations to unexisting bucket. Still need to make it configurable.
Updated by Sage Weil almost 13 years ago
- Target version set to v0.30
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 676
Updated by Sage Weil almost 13 years ago
- Target version deleted (
v0.30) - Translation missing: en.field_position deleted (
676) - Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 681
Updated by Sage Weil over 12 years ago
- Status changed from New to In Progress
- Assignee set to Yehuda Sadeh
- Target version set to v0.35
let's either add hte config option or close this bug.
Updated by Yehuda Sadeh over 12 years ago
- Status changed from In Progress to Resolved
config option done at commit:6506d43cbc2fd30b9907a1d0efe5d78ebf9fd6d3.
Updated by John Spray over 6 years ago
- Project changed from Ceph to rgw
- Category deleted (
22) - Target version deleted (
v0.35)
Bulk reassign of radosgw category to RGW project.
Actions