Actions
Issue #6253
closed
Chunked uploads don't work against S3
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Backlog
Sprint:
Sprint 69
Quarter:
Description
The problem is that we're storing chunks in S3 and then trying to write to these files. I think we need to either:
- Store the chunks on the filesystem and then when the upload is done, move it to s3
- Store the chunks in S3 and pull them down whenever a new chunk comes in, write to them, and then upload them back into S3
Updated by fao89 about 4 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 67
Updated by lmjachky about 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to lmjachky
Updated by pulpbot about 4 years ago
- Status changed from ASSIGNED to POST
Added by Lubos Mjachky about 4 years ago
Updated by Anonymous about 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|6a3efe7e82adab852c0a241f019565dd6ec72ceb.
Updated by ttereshc about 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Sprint/Milestone set to 3.3.0
Actions
.
Upload chunks to a local file system
As of now, every single chunk is going to be "uploaded" to a local file system instead of the defined default file storage.
In addition to that, the test test_delete_upload was refactored because it did not properly verify whether the committed upload was removed from the file system or not. It rather tested if the upload was deleted after sending an HTTP DELETE request.
closes #6253