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).."
Description of problem:
Syncing a custom repository to Capsule fails with:
Parsing interrupted: The repository metadata being synced into Pulp is erroneous in a way that makes it ambiguous (duplicate NEVRAs), and therefore we do not allow it to be synced in 'mirror_complete' mode. Please choose a sync policy which does not mirror repository metadata.
Please read https://github.com/pulp/pulp_rpm/issues/2402 for more details.
Version-Release number of selected component (if applicable):
How reproducible:
Easy
Steps to Reproduce:
1. create a custom repository for:
https://yum.enterprisedb.com/edb/redhat/rhel-8-x86_64/
You would need to register an account first:
https://www.enterprisedb.com/accounts/register
After successful registration go to the https://www.enterprisedb.com/software-downloads-postgres - chose Linux x86-64 Access repo
On that page you can generate Repository password.
2. after syncing, add it to a content view
3. sync the content view to a Capsule
Actual results:
The Capsule sync task fails with above error.
Expected results:
The Capsule sync task should finish successfully.
Additional info:
Update: I've reproduced a scenario where this can happen on my test system and verified that the patch works (the complex one that would be challenging to deploy as a hotfix).
I'm now working on a second patch which should be easier to deploy as a hotfix.
Comment 33pulp-infra@redhat.com
2022-08-09 10:20:21 UTC
The Pulp upstream bug status is at closed. Updating the external tracker on this bug.
Created attachment 1907644[details]
Hotfix RPM for Satellite 6.10.7
INSTALL INSTRUCTIONS:
1. Take a complete backup or snapshot of Satellite 6.10.7 server
2. Download the hotfix RPM for Satellite 6.10.7 attached to this BZ and copy it to Satellite server
3. # yum install ./python3-pulp-rpm-3.14.14-2.HOTFIXRHBZ2103522.el7pc.noarch.rpm --disableplugin=foreman-protector
4. # satellite-maintain service restart
AFTER HOTFIX INSTALLATION:
1. Regenerate Metadata for affected Content View Versions or standalone Repositories, following https://access.redhat.com/solutions/6663481
2. Sync the affected Capsules
@Marek, 6.11.3 is scheduled to get this fix (tracked as https://bugzilla.redhat.com/show_bug.cgi?id=2122173 for that release). If it is urgent then you can ask for one, though the fix should be available through standard channels in about 2.5 weeks.
Hotfix RPMs are available for this bug for Satellite 6.11.2 on RHEL7 and on RHEL8.
To obtain the hotfixes, please see the cloned bug https://bugzilla.redhat.com/show_bug.cgi?id=2122173 tracking this issue for the upcoming 6.11.3 release
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.12.0 snap 11 with python39-pulp-rpm-3.17.10-3.el8pc.noarch
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 (Important: Satellite 6.12 Release), 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/RHSA-2022:8506
Comment 67Red Hat Bugzilla
2023-09-18 04:40:57 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days