Bug 1992274

Summary: [pulp3] Content migration can fail for RPM content which is different but has the same relative path
Product: Red Hat Satellite Reporter: Tanya Tereshchenko <ttereshc>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lai <ltran>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9.0CC: ggainey, jjeffers, ltran, osousa, pcreech, rchan, satellite6-bugs, ttereshc
Target Milestone: 6.9.6Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-pulp-rpm-3.11.2,python-pulpcore-3.7.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1985958 Environment:
Last Closed: 2021-09-21 14:37:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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