Bug 2082224 - Syncing EPEL repos on Satellite 6.10 fails with: "Incoming and existing advisories have the same id but different timestamps and non-intersecting package lists.."
Summary: Syncing EPEL repos on Satellite 6.10 fails with: "Incoming and existing advis...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 6.10.6
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-05 15:21 UTC by Brad Buckingham
Modified: 2022-08-31 18:01 UTC (History)
22 users (show)

Fixed In Version: pulp_rpm-3.14.14
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2024963
Environment:
Last Closed: 2022-05-31 15:19:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulp_rpm issues 2422 0 None closed A common incoming/existing advisory conflict needs to be handled better 2022-05-05 15:22:10 UTC
Red Hat Knowledge Base (Solution) 6570731 0 None None None 2022-05-05 15:22:10 UTC
Red Hat Product Errata RHBA-2022:4850 0 None None None 2022-05-31 15:19:49 UTC

Comment 4 Lai 2022-05-18 19:04:24 UTC 
This is a difficult bz to verify.  The best I could do was sync an EPEL repo, then resync it several times to see if there's an issue.  So far, after 5 resyncs, the issue doesn't present itself.  I also checked the code base and everything is in there.

verified on 6.10.6 snap 2 with python3-pulp-rpm-3.14.14-1.el7pc.noarch
Comment 9 errata-xmlrpc 2022-05-31 15:19:38 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.10.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-2022:4850
Note You need to log in before you can comment on or make changes to this bug.