Description of problem:

Synchronize some packages of the public JFrog Repository (https://releases.jfrog.io/artifactory/jfrog-rpms/) to my capsules. I'm trying to sync the packages of jfrog-cli-v2-jf to my capsules, but the RPM's in the directory jfrog-cli-v2 have the same filename. This leads to the following error on capsule sync of the repo:

duplicate key value violates unique constraint "core_publishedartifact_publication_id_relative__97f785f4_uniq" DETAIL: Key (publication_id, relative_path)=(0195704c-632c-723c-8855-bf36387f4a52, Packages/j/jfrog-cli-2.38.1.x86_64.rpm) already exists.Could not lookup a publication_href for repo 25167

How reproducible:

I have test it on satellite server where sync the repo from the upstream url which will be successful sync .

The repository added to content view when published and promoted start the Capsule sync in background for the LCE promoted in the content view.

The Capsule sync which trigger for the content view publishing stops with below error.

duplicate key value violates unique constraint "core_publishedartifact_publication_id_relative__97f785f4_uniq" DETAIL: Key (publication_id, relative_path)=(0195704c-632c-723c-8855-bf36387f4a52, Packages/j/jfrog-cli-2.38.1.x86_64.rpm) already exists.Could not lookup a publication_href for repo 25167

Is this issue a regression from an earlier version:

Steps to Reproduce:

Create a Repository in Satellite from Upstream URL: https://releases.jfrog.io/artifactory/jfrog-rpms/

Create a Content View with this newly created Repository

Create a Filter in this Content View excluding e.g. "jfrog-artifactory-oss", shouldn't matter which one you use

Publish and Promote a new Version of this Content View, so it get's synced to your Capsule

Watch the Sync Task and see it fail with the error message:

duplicate key value violates unique constraint "core_publishedartifact_publication_id_relative__97f785f4_uniq"
DETAIL:  Key (publication_id, relative_path)=(0195a437-0760-7a4e-9f51-1a10affbaed4, Packages/j/jfrog-cli-2.38.1.x86_64.rpm) already exists.Could not lookup a publication_href for repo 25149

when the repository is filtered, it get's rebuilt in the background and then the error appears, when there is no filter applied to this repository, it just get's copied and not rebuilt and there is no error.

Actual behavior:
[Describe the issue in detail, including what is happening and where]

Expected behavior:
[Describe what should be happening instead]

Business Impact / Additional info:

Unable to install the package for the client which are registered to the capsule server.Without updates, your systems remain exposed to known security vulnerabilities, which attackers can exploit.