Juan,
You'll want to edit /usr/lib/systemd/system/pulp-api.service and set the
timeout option. This worked for me:
ExecStart=/usr/local/lib/pulp/bin/gunicorn pulpcore.app.wsgi:application \
--bind 'localhost:24817' \
--access-logfile - \
--timeout 180
Make sure you
Hi David,
On 5/07/19 16:27, David Davis wrote:
> I tested and confirmed that the files are not being deleted. Mind
> opening a bug for that?
I created an issue https://pulp.plan.io/issues/5092
>
> For the failed chunk uploads, httpie is timing out. You can set a
> higher timeout (like you did) or
I tested and confirmed that the files are not being deleted. Mind opening a
bug for that?
For the failed chunk uploads, httpie is timing out. You can set a higher
timeout (like you did) or use smaller chunks.
I looked into why artifact creation is failing for files < 2GB. The reason
is that it's
Hi David
This morning I made a test sequence and open a ticket
https://pulp.plan.io/issues/5087
Yes, I see that the update file is deleted when the artifact is created.
When I get the artifact creation error, the upload HREF is not deleted,
which could be normal as there was a error.
But when
Juan,
There is in fact a 2GB limit currently on artifact size. I consider this a
bug and I filed this issue:
https://pulp.plan.io/issues/4998
The file in /var/lib/pulp/upload should be deleted once it's imported as an
artifact. I'm guessing it's maybe not happening since the server is
throwing