[Pulp-list] Clean uploaded but not imported content

[Brian Bouterse]

I'm familiar with this limitation. You can manually delete them [0], but 
there is nothing in Pulp which cleans these up automatically as far as I 
know.

Pulp does have a monthly maintenance [1] codepath which could also 
delete unimported content. It could look for files older than some 
reasonable threshold like 2 weeks or something like that. Feel free to 
file the feature request if you want.

There is a plan for a new Upload API [2]. That plan will provide 
auto-cleanup so if [2] is implemented soon then we would no longer need 
the monthly cleanup story you might file.

[0]: 
http://docs.pulpproject.org/dev-guide/integration/rest-api/content/upload.html#delete-an-upload-request
[1]: 
https://github.com/pulp/pulp/blob/2ed8b7f51af53e7abd1748f663493b212411815b/server/pulp/server/maintenance/monthly.py#L22
[2]: https://pulp.plan.io/issues/892

-Brian


On 07/10/2016 10:18 PM, Rohan McGovern wrote:
>
> The pulp upload API docs [1] explain that uploading a unit to a repo is
> a 4 step process:
>
> 1. Make upload request
> 2. Upload the content (file)
> 3. Trigger importer(s), wait for their tasks to run
> 4. Delete upload request
>
> The process interacting with pulp's API might be prone to errors in
> steps 2 or 3, leaving unimported content behind on the server
> (e.g. files under /var/lib/pulp/uploads/ ).
>
> Is there any mechanism to periodically clean these up?
>
> If there's nothing already, would it be fair to include this in the
> scope of pulp or is it considered this should instead be handled externally?
>
> [1] https://docs.pulpproject.org/dev-guide/integration/rest-api/content/upload.html
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>