Actions
Bug #39632
closedlifecycle transitions on non existent placement targets
% Done:
0%
Source:
Tags:
lifecycle
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Currently we don't error when a non existent placement target is supplied in lifecycle, which ends with the object being transitioned to the standard storage class itself.
eg. brokentransition.json { "Rules": [ { "Transition" : { "Days": 10, "StorageClass": "kitchensink" }, "ID": "Transition abc objects", "Status": "Enabled", "Prefix":"abc" } ] }
aws s3api put-bucket-lifecycle & putting an object that matches the prefix will lead to the object being reported as transitioned to the non existant storage class and just being copied in the same standard pool
Updated by Casey Bodley almost 5 years ago
- Status changed from New to 7
- Assignee set to Abhishek Lekshmanan
- Tags set to lifecycle
- Backport set to nautilus
- Pull request ID set to 28256
Updated by Casey Bodley almost 5 years ago
- Status changed from 7 to Pending Backport
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40849: nautilus: lifecycle transitions on non existent placement targets added
Updated by Nathan Cutler over 4 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