Expiring Large Objects doesn't clean up segments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-swiftclient |
New
|
Undecided
|
Unassigned |
Bug Description
When creating a Large Object with an expirer header the user should expect that all of the segments (and not just the manifest) are expired according to the requested header:
vagrant@
testme.builder segment 2
testme.builder segment 0
testme.builder segment 1
testme.builder
^ object and segments are uploaded with x-delete-after but only manifest gets the expire header
vagrant@
testme.
testme.
testme.
vagrant@
URL: http://
Auth Token: AUTH_tka3462447
Account: AUTH_test
Container: test_segments
Object: testme.
Content Type: application/
Content Length: 1048576
Last Modified: Mon, 09 Nov 2015 22:04:06 GMT
ETag: cd777a16f729091
Accept-Ranges: bytes
X-Timestamp: 1447106645.10095
X-Trans-Id: tx4ae8960d734a4
vagrant@
Object HEAD failed: http://
^ manifest is 404'd but segments remain