SLO upload doesn't check /info before sending
Bug #1524465 reported by
Douglas Soltesz
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-swiftclient |
In Progress
|
Undecided
|
Cheng Li |
Bug Description
When uploading a SLO Swiftclient sends the data first to the multipart_segments then creates the SLO manifest.
This fails if:
the SLO segments exceed the max allowed segments
the SLO segment size is larger than the size specified by the user
SLO middleware is not enabled
However, by the time this is detected, my time and bandwidth have been wasted.
If swiftclient was to check /info before sending SLO/DLOs the system can abort before the transfer.
Thanks,
Doug
Changed in python-swiftclient: | |
assignee: | nobody → Cheng Li (shcli) |
Changed in python-swiftclient: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Also note that in some (all?) of these situations, the orphaned segments are left on the server!