Issue #7290: `None` error with RPM Copy API - RPM Support - Pulp

Actions

Send by e-mail Copy link

Issue #7290

closed

`None` error with RPM Copy API

Added by iballou over 4 years ago. Updated over 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

dalley

Sprint/Milestone:

3.6.2

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 79

Quarter:

Description

When trying to copy content, my Pulp worker was dying. These logs were all I could see that was related:

Aug 05 18:07:02 centos7-katello-devel-2.cannolo.example.com pulpcore-resource-manager[4005]: pulp: rq.worker:INFO: resource-manager: Job OK (05b323d1-d351-47d1-94a7-99cf1d0396e4)
Aug 05 18:07:02 centos7-katello-devel-2.cannolo.example.com pulpcore-worker-2[4129]: python3: ../src/repodata.c:2929: repodata_add_dirstr: Assertion `dir' failed.
Aug 05 18:07:02 centos7-katello-devel-2.cannolo.example.com pulpcore-worker-2[4129]: pulp: rq.worker:WARNING: Moving job to FailedJobRegistry (work-horse terminated unexpectedly; waitpid returned 6)

Repo that I used: https://fixtures.pulpproject.org/srpm-unsigned/

Unfortunately after re-writing some of my tests I am unable to reproduce the issue.

Pulp RPM 3.4.1

Actions

Copy link

Updated by dalley over 4 years ago

iballou, which content unit(s) were you attempting to copy? Do you know which particular options were being used?

Actions

Copy link

Updated by iballou over 4 years ago

dalley, all content (the 3 srpms) were being copied. It was a simple case, one source repo copying content to a dest repo. No dependency solving, no dest_base_version.

Actions

Copy link