Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1992274 - [pulp3] Content migration can fail for RPM content which is different but has the same relative path
Summary: [pulp3] Content migration can fail for RPM content which is different but has...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 6.9.6
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-10 20:31 UTC by Tanya Tereshchenko
Modified: 2021-09-21 14:37 UTC (History)
8 users (show)

Fixed In Version: python-pulp-rpm-3.11.2,python-pulpcore-3.7.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1985958
Environment:
Last Closed: 2021-09-21 14:37:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 9227 0 Normal CLOSED - CURRENTRELEASE Backport #8133 "Same package from different repos yields error on sync" to 3.7.z 2021-08-24 21:07:26 UTC
Pulp Redmine 9228 0 Normal CLOSED - CURRENTRELEASE Backport the relative path fix "fix_mismatched_remote_artifacts" to 3.11.z 2021-08-24 23:08:11 UTC
Red Hat Product Errata RHBA-2021:3628 0 None None None 2021-09-21 14:37:32 UTC

Description Tanya Tereshchenko 2021-08-10 20:31:58 UTC 
Description of problem:
If Pulp 2 has different packages under the same relative path, content migration (the publication creation part) will fail.

E.g. repo A has a package with NEVRA1 and relative path foo.rpm
 and repo B has a package with NEVRA2 and the same relative path foo.rpm.


Version-Release number of selected component (if applicable):
pulpcore 3.7
pulp_rpm 3.10

Similar to the sync problem in Bug 1985958.
Comment 3 pulp-infra@redhat.com 2021-08-10 23:11:40 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2021-08-10 23:11:41 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 5 pulp-infra@redhat.com 2021-08-10 23:11:43 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 6 pulp-infra@redhat.com 2021-08-10 23:11:45 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 7 pulp-infra@redhat.com 2021-08-22 21:06:43 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 8 pulp-infra@redhat.com 2021-08-22 22:07:46 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 9 pulp-infra@redhat.com 2021-08-23 16:11:20 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 10 pulp-infra@redhat.com 2021-08-24 15:08:23 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 11 pulp-infra@redhat.com 2021-08-24 15:08:25 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 12 pulp-infra@redhat.com 2021-08-24 21:07:27 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 13 pulp-infra@redhat.com 2021-08-24 23:08:12 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 14 Lai 2021-09-13 15:45:33 UTC 
Steps to retest:

1. Create a product and 2 custom repos for:
   - https://packages.grafana.com/oss/rpm
   - http://ftp.cs.stanford.edu/centos/7/opstools/x86_64/
2. Sync the repos
3. Perform migration
4. Check migration status


Expected:
Migration should complete without errors

Actual:
Migration completed without errors.

Running the migration stats gives:
Running Retrieve Pulp 2 to Pulp 3 migration statistics
================================================================================
Retrieve Pulp 2 to Pulp 3 migration statistics: 
============Migration Summary================
Migrated/Total RPMs: 1415/1415
Migrated/Total errata: 0/0
Migrated/Total repositories: 2/2

Estimated migration time based on yum content: fewer than 5 minutes

Checked pulp cli as well and repos are present in the db.

Verified on 6.9.6_02 with python3-pulp-rpm-3.11.2-1.el7pc.noarch and python3-pulpcore-3.7.8-1.el7pc.noarch
Comment 19 errata-xmlrpc 2021-09-21 14:37:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.9.6 Async Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:3628
Note You need to log in before you can comment on or make changes to this bug.