Issue #5085
closedunable to sync EPEL7 RPM remote: "No declared artifact with relative path \"\" for content \"<Package: cowsay>\"",
Description
Hi Guys
I am unable to sync the Extra Packages for Enterprise Linux (EPEL) 7 remote with a repository. The tasks ends with the error below. I tested different policies (immediate, on_demand) and with or without validation. The result is always the same. Other RPM remotes are syncing fine. Pulp 3 was installed using the ansible installation method.
If you need me to do any further testing please let me know.
Thanks
---
Steps to reproduce:
http POST http://localhost:24817/pulp/api/v3/remotes/rpm/rpm/ name='epel7-x86_64' url='https://dl.fedoraproject.org/pub/epel/7/x86_64/' policy='on_demand'
http POST http://localhost:24817/pulp/api/v3/repositories/ name='epel7-x86_64'
export REMOTE_HREF=$(http :24817/pulp/api/v3/remotes/rpm/rpm/ | jq -r '.results[] | select(.name == "epel7-x86_64") | ._href')
export REPO_HREF=$(http :24817/pulp/api/v3/repositories/ | jq -r '.results[] | select(.name == "epel7-x86_64") | ._href')
http POST :24817${REMOTE_HREF}sync/ repository=$REPO_HREF
Result:
{
"_created": "2019-07-04T14:47:04.436912Z",
"_href": "/pulp/api/v3/tasks/1309ad44-3111-4cf4-a4c9-1243295818fb/",
"created_resources": [],
"error": {
"code": null,
"description": "No declared artifact with relative path \"\" for content \"<Package: cowsay>\"",
"traceback": " File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/worker.py\", line 812, in perform_job\n rv = job.perform()\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py\", line 588, in perform\n self._result = self._execute()\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py\", line 594, in _execute\n return self.func(*self.args, **self.kwargs)\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 67, in synchronize\n dv.create()\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/plugin/stages/declarative_version.py\", line 169, in create\n loop.run_until_complete(pipeline)\n File \"/usr/lib64/python3.6/asyncio/base_events.py\", line 484, in run_until_complete\n return future.result()\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/plugin/stages/api.py\", line 209, in create_pipeline\n await asyncio.gather(*futures)\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/plugin/stages/api.py\", line 43, in __call__\n await self.run()\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/plugin/stages/artifact_stages.py\", line 217, in run\n RemoteArtifact.objects.bulk_get_or_create(self._needed_remote_artifacts(batch))\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/plugin/stages/artifact_stages.py\", line 260, in _needed_remote_artifacts\n c=d_content.content))\n"
},
"finished_at": "2019-07-04T14:47:31.442835Z",
"name": "pulp_rpm.app.tasks.synchronizing.synchronize",
"non_fatal_errors": [],
"parent": null,
"progress_reports": [
{
"done": 5,
"message": "Downloading and Parsing Metadata",
"state": "canceled",
"suffix": "",
"task": "/pulp/api/v3/tasks/1309ad44-3111-4cf4-a4c9-1243295818fb/",
"total": 5
},
{
"done": 206,
"message": "Downloading Artifacts",
"state": "canceled",
"suffix": "",
"task": "/pulp/api/v3/tasks/1309ad44-3111-4cf4-a4c9-1243295818fb/",
"total": 206
},
{
"done": 5502,
"message": "Associating Content",
"state": "canceled",
"suffix": "",
"task": "/pulp/api/v3/tasks/1309ad44-3111-4cf4-a4c9-1243295818fb/",
"total": 5502
}
],
"spawned_tasks": [],
"started_at": "2019-07-04T14:47:04.512453Z",
"state": "failed",
"worker": "/pulp/api/v3/workers/22d38b77-2067-4811-a52e-7e90f98d4122/"
}
Updated by amacdona@redhat.com almost 5 years ago
- Project changed from Pulp to RPM Support
- Sprint/Milestone deleted (
3.0.0)
Updated by ipanova@redhat.com almost 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to lmjachky
Updated by lmjachky almost 5 years ago
I was trying to reproduce the issue but with no success. I got the following response when I run the included code snippet.
{
"task": "/pulp/api/v3/tasks/862bd99d-ffd7-4ed2-bf62-0ff14406e152/"
}
After some period of time, the task was completed successfully, when I run:
http http://localhost:24817/pulp/api/v3/tasks/862bd99d-ffd7-4ed2-bf62-0ff14406e152/
{
"_created": "2019-07-15T15:18:34.642491Z",
"_href": "/pulp/api/v3/tasks/862bd99d-ffd7-4ed2-bf62-0ff14406e152/",
"created_resources": [
"/pulp/api/v3/repositories/98c271e1-af1a-45b2-9ff5-169d74306767/versions/1/"
],
"error": null,
"finished_at": "2019-07-15T15:39:04.167406Z",
"name": "pulp_rpm.app.tasks.synchronizing.synchronize",
"non_fatal_errors": [],
"parent": null,
"progress_reports": [
{
"done": 5,
"message": "Downloading Metadata Files",
"state": "completed",
"suffix": null,
"total": 5
},
{
"done": 13327,
"message": "Parsed Packages",
"state": "completed",
"suffix": null,
"total": 13327
},
{
"done": 13327,
"message": "Downloading Artifacts",
"state": "completed",
"suffix": null,
"total": 13327
},
{
"done": 17655,
"message": "Associating Content",
"state": "completed",
"suffix": null,
"total": 17655
},
{
"done": 4328,
"message": "Parsed Erratum",
"state": "completed",
"suffix": null,
"total": 4328
}
],
"spawned_tasks": [],
"started_at": "2019-07-15T15:18:34.726300Z",
"state": "completed",
"worker": "/pulp/api/v3/workers/d8cbeb5a-7002-44d1-9dbd-0158d4e30312/"
}
Are you still having the issues while syncing the remote? The remote content was updated. Maybe, there were introduced some corrupted files which caused this behavior.
Updated by lmjachky over 4 years ago
- Status changed from ASSIGNED to CLOSED - WORKSFORME