Issue #3388
closed
Syncing Debian (Ubuntu) example repo fails
Description
When attempting to sync a deb repository using the documented Ubuntu example, I am encountering the following error.
[Errno 2] No such file or directory:
u'/var/cache/pulp/reserved_resource_worker-0@pulp.mydomain.dev/06f8363
6-5faf-455b-b73c-a6794309ccfb/packages/00/04/python-all_2.7.11-1_amd64.deb'
The commands I used to create and sync the repo are as follows.
pulp-admin deb repo create --repo-id 'xenial-amd64' --feed 'http://de.archive.ubuntu.com/ubuntu' --releases 'xenial' --components 'main' --architectures 'amd64'
pulp-admin deb repo sync run --repo-id xenial-amd64
I've attached a snippet from /var/log/messages and am running the following Pulp versions.
pulp 2.15.1-1
pulp_deb 1.6.0-1
Files
Updated by dalley almost 7 years ago
- Project changed from Pulp to Debian Support
Updated by dalley almost 7 years ago
- Project changed from Debian Support to Pulp
Updated by dalley almost 7 years ago
- Project changed from Pulp to Debian Support
- Triaged changed from No to Yes
Updated by taylorcw almost 7 years ago
This is probably due to the get request timing out so the package didn't actually download.
EDIT:
/usr/lib/python2.7/site-packages/nectar/config.py
Change the "read_timeout=27" value to 600. Restart services and try a new sync. This fixed the issue for me.
Updated by signed8bit almost 7 years ago
That does not seem to work for me. I have read_timeout=600 in /usr/lib/python2.7/site-packages/nectar/config.py and still encounter errors during sync.
Task Failed
[Errno 2] No such file or directory:
u'/var/cache/pulp/reserved_resource_worker-0@pulp.mydomain.dev/129b54e
e-a4f0-49d7-a1b0-bc1075a9c578/packages/00/20/librest-0.7-0-dbg_0.7.93-1_amd64.de
b'
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 5 years ago
- Status changed from CLOSED - WONTFIX to NEW
Was closed as part of Pulp2 mass-fix, but reopening so the Debian plugin devs can determine what they want to do.
Updated by mdellweg over 5 years ago
- Status changed from NEW to CLOSED - NOTABUG
We believe, this to be a transient occurrence due to a failed download.
.