Bug 2122173

Summary: Capsule sync fails with "Parsing interrupted: The repository metadata being synced into Pulp is erroneous in a way that makes it ambiguous (duplicate NEVRAs).."
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lai <ltran>
Severity: high Docs Contact:
Priority: high    
Version: 6.10.6CC: akapse, avnkumar, aymeric.marchal, dalley, dkliban, ggainey, hyu, jbhatia, jfindysz, jsenkyri, kkinge, lblicha, ldelouw, marek.moldauer, momran, msunil, pbadguja, pmoravec, rchan, saime, saydas, sboyron, snemeth, wclark, wpinheir
Target Milestone: 6.11.3Keywords: Regression, Triaged
Target Release: Unused   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: pulp_rpm 3.17.10 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2103522 Environment:
Last Closed: 2022-09-28 16:28:48 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:
Attachments:
Description Flags
Hotfix RPM for Satellite 6.11.2 on RHEL7
none
Hotfix RPM for Satellite 6.11.2 on RHEL8 none

Comment 3 Lai 2022-09-12 17:21:49 UTC 
Steps to test

1. Create a product
2. Create 3 custom yum repos for the following:

https://rpm.releases.hashicorp.com/fedora/35/x86_64/stable/
https://yum.centreon.com/standard/21.10/el7/stable/x86_64/
http://mirror.centos.org/centos/7/opstools/x86_64/

3. Choose 'Additive', 'Content Only', or 'Complete Mirroring' for the repos.  Insure each repo has a different selection
4. Sync the custom repos
5. Create a cv and add the repos
6. Spin up a capsule and register it to satellite
7. Publish the cv
8. Check the auto capsule sync
9. You can also manually trigger a complete sync by going to infrastructure -> capsule -> <select capsule> -> complete sync


Expected result:
Capsule should sync without issues in both cases

Actual:
Capsule sync without issues in both cases

After registering the capsule to satellite with the ak, I was able to do yum repolist and get the synced repos.

Verified on 6.11.3 with python38-pulp-rpm-3.17.10-2.el8pc.noarch on rhel8 and rhel7
Comment 4 wclark 2022-09-13 17:33:42 UTC 
Created attachment 1911571 [details]
Hotfix RPM for Satellite 6.11.2 on RHEL7

INSTALL INSTRUCTIONS:

1. Take a complete backup or snapshot of Satellite 6.11.2 server

2. Download the Hotfix RPM for Satellite 6.11.2 on RHEL7 attached to this BZ and copy it to Satellite server

3. # yum install ./tfm-pulpcore-python3-pulp-rpm-3.17.10-2.el7pc.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart

AFTER HOTFIX INSTALLATION:

1. Sync the affected Capsules
Comment 5 wclark 2022-09-13 17:37:45 UTC 
Correction to the above instructions 'AFTER HOTFIX INSTALLATION':

Before syncing the affected Capsules, it is necessary to also install the Hotfix RPM on the Capsules so that they can sync the duplicated NEVRAs. The steps to install the hotfix on a Capsule server are the same.
Comment 6 wclark 2022-09-13 17:41:17 UTC 
Created attachment 1911575 [details]
Hotfix RPM for Satellite 6.11.2 on RHEL8

INSTALL INSTRUCTIONS:

1. Take a complete backup or snapshot of Satellite 6.11.2 server

2. Download the Hotfix RPM for Satellite 6.11.2 on RHEL8 attached to this BZ and copy it to Satellite server

3. # yum install ./python38-pulp-rpm-3.17.10-2.el8pc.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart

5. Repeat the above steps to install the same pulp-rpm plugin hotfix on each Capsule server

AFTER HOTFIX INSTALLATION:

1. Sync the affected Capsules
Comment 11 errata-xmlrpc 2022-09-28 16:28:48 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.11.3 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-2022:6743