Actions
Bug #18989
closedrgw_file: allow setattr on placeholder (common_prefix) directories
% Done:
0%
Source:
Tags:
Backport:
jewel kraken
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When a POSIX path <bucket>/foo/ is known only as an implicit path segment from other objects (e.g., <bucket>/foo/bar.txt), as case that would usually arise from S3 upload of such an object, an RGWFileHandle object representing "<bucket>/foo/" will be constructed as needed, with no backing in RGW.
This is by design, but subsequently, if a setattr is performed on such a handle, we must be ready to create the object inline with storing the attributes. This case is/was not handled.
Updated by Matt Benjamin about 7 years ago
- Status changed from In Progress to Pending Backport
Updated by Matt Benjamin about 7 years ago
- Backport changed from jewel to jewel kraken
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #19169: jewel: rgw_file: allow setattr on placeholder (common_prefix) directories added
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #19170: kraken: rgw_file: allow setattr on placeholder (common_prefix) directories added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions