Bug #37879
rgw: fix prefix handling in LCFilter
0%
Description
A lifecycle configuration document such as the following is legal (see examples at https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html), but was rejected due to RGW-internal prefix handling.
"""
<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Rule>
<ID>delete-7-days</ID>
<Filter>
<Tag>
<Key>suffix</Key>
<Value>WMV</Value>
</Tag>
</Filter>
<Status>Enabled</Status>
<Expiration>
<Days>7</Days>
</Expiration>
</Rule>
<Rule>
<ID>delete-8-days</ID>
<Filter>
<Tag>
<Key>tim</Key>
<Value>tam</Value>
</Tag>
</Filter>
<Status>Enabled</Status>
<Expiration>
<Days>8</Days>
</Expiration>
</Rule>
</LifecycleConfiguration>
"""
Related issues
History
#1 Updated by Matt Benjamin about 5 years ago
- Status changed from In Progress to Fix Under Review
#2 Updated by Matt Benjamin about 5 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to mimic,luminous
#3 Updated by Nathan Cutler about 5 years ago
- Copied to Backport #38368: luminous: rgw: fix prefix handling in LCFilter added
#4 Updated by Nathan Cutler about 5 years ago
- Copied to Backport #38369: mimic: rgw: fix prefix handling in LCFilter added
#5 Updated by Matt Benjamin about 5 years ago
#6 Updated by Matt Benjamin about 5 years ago
@smithfarm, @asingh, this PR replaces the prior change
#7 Updated by Nathan Cutler about 5 years ago
- Status changed from Pending Backport to New
waiting for new master fix
#8 Updated by Casey Bodley about 5 years ago
- Duplicated by Bug #38758: rgw: put lifecycle configuration fails if Prefix is not set (2) added
#9 Updated by Matt Benjamin almost 5 years ago
- Status changed from New to Pending Backport
- Backport changed from mimic,luminous to nautilus,mimic,luminous
#10 Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40007: nautilus: rgw: fix prefix handling in LCFilter added
#11 Updated by Nathan Cutler almost 5 years ago
- Pull request ID set to 26518
#12 Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved