Ceph » rgw

Bug #39632

Updated by Abhishek Lekshmanan almost 5 years ago

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. 

 <pre> 
 eg. brokentransition.json 
 { "Rules": [ 
             { 
                 "Transition" : { 
                     "Days": 10, 
                     "StorageClass": "kitchensink" 
                 }, 
                 "ID": "Transition abc objects", 
                 "Status": "Enabled", 
                 "Prefix":"abc" 
             } 
 ] 
 } 
 </pre> 

 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  

Back