Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Capsule sync fails with "Parsing interrupted: The repository metadata being synced into Pulp is erroneous in a way that makes it ambiguous (duplicate NEVRAs).."
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
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
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.
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
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