Problem:
When attempting to sync multiple releases (buster bullseye) and components (puppet5 puppet6) using pulp3 I receive the following error:
duplicate key value violates unique constraint “core_publishedartifact_publication_id_relative__97f785f4_uniq”
DETAIL: Key (publication_id, relative_path)=(d6cc6b21-1ae5-40ac-8809-50f5bea8c040, pool/all/p/pdk/pdk_2.3.0.0-1buster_amd64.deb) already exists.
I currently have a single product for “puppet” Should I just separate out the different releases? I believe this is just due to the way the simple publisher works, correct?
Expected outcome:
Successfully sync and publish a mirror of the upstream repos.
Foreman and Proxy versions:
Foreman 3.0.1, Katello 4.2.1
python3-pulp-deb-2.14.1-2.el7.noarch
Distribution and version:
CentOS 7
Other relevant data: