Project

General

Profile

Bug #18989

rgw_file: allow setattr on placeholder (common_prefix) directories

Added by Matt Benjamin 4 months ago. Updated 4 months ago.

Status:
Pending Backport
Priority:
High
Assignee:
Target version:
-
Start date:
02/19/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
jewel kraken
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Needs Doc:
No

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.


Related issues

Copied to rgw - Backport #19169: jewel: rgw_file: allow setattr on placeholder (common_prefix) directories Resolved
Copied to rgw - Backport #19170: kraken: rgw_file: allow setattr on placeholder (common_prefix) directories In Progress

History

#1 Updated by Matt Benjamin 4 months ago

  • Status changed from In Progress to Pending Backport

#2 Updated by Matt Benjamin 4 months ago

  • Backport changed from jewel to jewel kraken

#3 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #19169: jewel: rgw_file: allow setattr on placeholder (common_prefix) directories added

#4 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #19170: kraken: rgw_file: allow setattr on placeholder (common_prefix) directories added

Also available in: Atom PDF