Sync for EPEL repositories fails with: "Incoming and existing advisories have the same id but different timestamps and non-intersecting package lists" on Red Hat Satellite.

Solution Verified - Updated

Environment

  • Red Hat Satellite 6.10

Issue

  • Synchronization task for EPEL repositories fails with an error similar to:

    Katello::Errors::Pulp3Error
Incoming and existing advisories have the same id but different timestamps and non-intersecting package lists. It is likely that they are from two different incompatible remote repositories. E.g. RHELX-repo and RHELY-debuginfo repo. Ensure that you are adding content for the compatible repositories. To allow this behavior, set ALLOW_AUTOMATIC_UNSAFE_ADVISORY_CONFLICT_RESOLUTION = True (q.v.) in your configuration. Advisory id: FEDORA-EPEL-2016-f74772a384

Resolution

  • As a workaround please go ahead and set PULP_ALLOW_AUTOMATIC_UNSAFE_ADVISORY_CONFLICT_RESOLUTION=True in pulp settings:

  1. Create '/etc/systemd/system/pulpcore-worker@.service.d/' directory:

    # mkdir /etc/systemd/system/pulpcore-worker@.service.d/

  2. Create the following file:

    # vi /etc/systemd/system/pulpcore-worker@.service.d/settings.conf
###
[Service]
User=pulp
Environment=PULP_ALLOW_AUTOMATIC_UNSAFE_ADVISORY_CONFLICT_RESOLUTION=True
###

  3. Restart services:

    # systemctl daemon-reload
# foreman-maintain service restart

  4. Now re-synchronize the EPEL repository using below steps.

    Login to Satellite Web UI -> Navigate to Content -> Products -> Product_Name -> Click on the "Repository_Name" -> Select Action -> Advanced Sync -> Complete Sync.

Note: Perform above synchronization steps only for EPEL repository and not for Red Hat repositories.

For more KB articles/solutions related to Red Hat Satellite 6.x Repository Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Repository Issues.

For more KB articles/solutions related to Red Hat Satellite 6.x Pulp 3.0 Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Pulp 3.0-related Issues

Root Cause

  • This error doesn't occur on fresh Satellite 6.10 install. It only happens if the EPEL repo was previously sync'd on Satellite version using pulp2.
  • For more information please refer to This content is not included.Bug 2024963.
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.