Description of problem: Importing library with overlapping content on repositories may still hit a condition to fail with unique-constraint, even after [1] [1] https://pulp.plan.io/issues/8633 Version-Release number of selected component (if applicable): How reproducible: Unsure Steps to Reproduce: 1. Have multiple repositories with overlapping content 2. Export the the entire library 3. Import the library (??) Actual results: Import tasks may fail Expected results: Import task should not fail Additional info: Feb 18 16:37:09 satellite pulpcore-worker-16: pulp [c4544ea4-4cbb-496b-868b-e2362973317b]: pulpcore.app.tasks.importer:INFO: ...1 import-errors encountered importing pulp_rpm.app.modelresource.PackageResource.json from repository-Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7Server-45550_9, retrying Feb 18 16:45:06 satellite pulpcore-worker-16: pulp [c4544ea4-4cbb-496b-868b-e2362973317b]: pulpcore.app.tasks.importer:ERROR: FATAL import-failure importing pulp_rpm.app.modelresource.PackageResource.json from repository-Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7Server-45550_9
Steps to retest: 1. Have multiple repositories with overlapping content (I chose rhel7) 2. Export the the entire library 3. Import the library Expected result: Import should be successful and contains all the library content Actual result: Import is successful and contains all the library content There's no concrete way to test this since it was observed in RHEL7 and on one customer db. Verified on 6.11 snap 23 with python38-pulpcore-3.16.8-2.el8pc.noarch
Requesting needsinfo from upstream developer dkliban, ggainey because the 'FailedQA' flag is set.
Moving to POST based upon discussion in Satellite standup.
Steps to retest: 1. Have multiple repositories with overlapping content (I chose rhel7) 2. Export the the entire library 3. Import the library Expected result: Import should be successful and contains all the library content Actual result: Import is successful and contains all the library content There's no concrete way to test this since it was observed in RHEL7 and on one customer db. Verified in 6.12 snap 7
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days