Issue #4520
closeddeb packages are not being synced
Description
Hi,
I'm trying to create a local Ubuntu repo cloning the packages but for some reason, the sync process finishes as completed and success after does not sync any package.
deb (Ubuntu) repo creation step:
pulp-admin deb repo create --repo-id 'xenial-amd64' --serve-http true --serve-https true --remove-missing true --relative-url=ubuntu/xenial/main --releases 'xenial' --components 'main' --architectures 'amd64' --feed 'http://us.archive.ubuntu.com/ubuntu'
Successfully created repository [xenial-amd64]
Sync command and output:
pulp-admin deb repo sync run --repo-id 'xenial-amd64'
+----------------------------------------------------------------------+
Synchronizing Repository [xenial-amd64]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Task Succeeded
[/]
Waiting to begin...
Publishing modules
[ ] 0%
1 of 7322 items
... completed
Publishing files to web
[/]
... completed
Writing Listings File
[\]
... completed
Writing Listings File
[-]
... completed
Task Succeeded
I have tried twice the sync step and the result is the same but I realized that operation deferred_download failed both tries.
Operations: sync
Resources: xenial-amd64 (repository)
State: Successful
Start Time: 2019-03-08T08:30:21Z
Finish Time: 2019-03-08T08:48:17Z
Task Id: af6094ba-6c8e-4f0a-aa29-64f81c296319
Worker Name: reserved_resource_worker-1@s5lpulp00001.nike.com
Operations: deferred_download
Resources:
State: Failed
Start Time: Unstarted
Finish Time: 2019-03-08T08:43:07Z
Task Id: 9f58916c-595f-4429-bb26-18747d1d4a2b
Worker Name: None
Operations: publish
Resources: xenial-amd64 (repository)
State: Successful
Start Time: 2019-03-08T08:48:23Z
Finish Time: 2019-03-08T09:04:15Z
Task Id: 56dfce8c-4edc-4739-9b5e-14d5379a71b7
Worker Name: reserved_resource_worker-1@s5lpulp00001.nike.com
Operations: deferred_download
Resources:
State: Failed
Start Time: 2019-03-08T09:13:06Z
Finish Time: 2019-03-08T09:13:07Z
Task Id: 8dd7d3f2-a9af-45ef-b5cb-e14c245b33c1
Worker Name: reserved_resource_worker-0@s5lpulp00001.nike.com
Operations: sync
Resources: xenial-amd64 (repository)
State: Successful
Start Time: 2019-03-08T09:23:07Z
Finish Time: 2019-03-08T09:31:50Z
Task Id: 324e191d-1b36-45b3-b933-52864cdb593a
Worker Name: reserved_resource_worker-1@s5lpulp00001.nike.com
Operations: publish
Resources: xenial-amd64 (repository)
State: Successful
Start Time: 2019-03-08T09:31:51Z
Finish Time: 2019-03-08T09:47:27Z
Task Id: 19da3a5e-e4b4-4884-8091-c1dc034e8a6f
Worker Name: reserved_resource_worker-1@s5lpulp00001.nike.com
Operations: deferred_download
Resources:
State: Failed
Start Time: 2019-03-08T09:43:06Z
Finish Time: 2019-03-08T09:43:07Z
Task Id: 67bb6fac-1744-48c3-b7d3-8213329866fe
Worker Name: reserved_resource_worker-3@s5lpulp00001.nike.com
This is our sandbox environment and we can make any test that you suggest.
Here details about the installation:
pulp-admin status
+----------------------------------------------------------------------+
Status of the server
+----------------------------------------------------------------------+
Api Version: 2
Database Connection:
Connected: True
Known Workers:
_id: scheduler@s5lpulp00001.nike.com
_ns: workers
Last Heartbeat: 2019-03-08T10:04:09Z
_id: resource_manager@s5lpulp00001.nike.com
_ns: workers
Last Heartbeat: 2019-03-08T10:04:11Z
_id: reserved_resource_worker-0@s5lpulp00001.nike.com
_ns: workers
Last Heartbeat: 2019-03-08T10:04:09Z
_id: reserved_resource_worker-2@s5lpulp00001.nike.com
_ns: workers
Last Heartbeat: 2019-03-08T10:04:07Z
_id: reserved_resource_worker-1@s5lpulp00001.nike.com
_ns: workers
Last Heartbeat: 2019-03-08T10:04:08Z
_id: reserved_resource_worker-3@s5lpulp00001.nike.com
_ns: workers
Last Heartbeat: 2019-03-08T10:04:08Z
Messaging Connection:
Connected: True
Versions:
Platform Version: 2.18
And the packages installed:
python-pulp-rpm-common-2.18.0-1.el7.noarch
python-pulp-oid_validation-2.18.0-2.el7.noarch
pulp-python-plugins-2.0.3-1.el7.noarch
pulp-python-admin-extensions-2.0.3-1.el7.noarch
python-pulp-docker-common-3.2.2-1.el7.noarch
python-pulp-repoauth-2.18.0-2.el7.noarch
pulp-server-2.18.0-2.el7.noarch
pulp-puppet-plugins-2.18.0-1.el7.noarch
pulp-docker-plugins-3.2.2-1.el7.noarch
python-pulp-bindings-2.18.0-2.el7.noarch
pulp-rpm-admin-extensions-2.18.0-1.el7.noarch
pulp-docker-admin-extensions-3.2.2-1.el7.noarch
python-pulp-python-common-2.0.3-1.el7.noarch
pulp-rpm-plugins-2.18.0-1.el7.noarch
pulp-ostree-plugins-1.3.1-1.el7.noarch
pulp-puppet-tools-2.18.0-1.el7.noarch
pulp-admin-client-2.18.0-2.el7.noarch
pulp-ostree-admin-extensions-1.3.1-1.el7.noarch
python-pulp-deb-common-1.8.0-1.el7.noarch
pulp-selinux-2.18.0-2.el7.noarch
python2-solv-0.6.34-2.pulp.el7.x86_64
pulp-deb-plugins-1.8.0-1.el7.noarch
python-pulp-client-lib-2.18.0-2.el7.noarch
pulp-deb-admin-extensions-1.8.0-1.el7.noarch
python-pulp-common-2.18.0-2.el7.noarch
python-pulp-ostree-common-1.3.1-1.el7.noarch
libsolv-0.6.34-2.pulp.el7.x86_64
pulp-puppet-admin-extensions-2.18.0-1.el7.noarch
python-pulp-puppet-common-2.18.0-1.el7.noarch
Updated by daviddavis almost 6 years ago
- Project changed from RPM Support to Debian Support
- Category changed from 22 to 16
Updated by quba42 over 5 years ago
Does not explain that the task finishes successfully, but is it possible there are some weird networking effects at work here?
Have you tried manually downloading a package within your sandbox environment?
Your command looks correct. Since others have successfully synced ubuntu repositories it must be something specific to your setup...
Updated by flamarion over 5 years ago
Actually, I did manage to sync the packages, but it's taking a loooooong time to finish since the sync up to the publishing. I think this is not a high priority anymore but I realize the publication task is consuming all memory and, somethings, celery is crashing and the task canceled.
Updated by quba42 about 4 years ago
- Status changed from NEW to CLOSED - NOTABUG
Given the latest update to the ticket: There won't be any further performance improvements for Pulp 2.
If you are having performance problems with Pulp 3, feel free to open a new ticket!