When attempts to sync capulse with 8 pulpcore workers sync gets: duplicate key value violates unique constraint "core_repositoryversion_repository_id_number_3c54ce50_uniq" DETAIL: Key (repository_id, number)=(8483dc67-8401-47ba-bb80-203f5a9c0429, 2) already exists. duplicate key value violates unique constraint "core_repositoryversion_repository_id_number_3c54ce50_uniq" DETAIL: Key (repository_id, number)=(cb12fe97-4c5f-4424-a1ee-e4ff550dd46f, 2) already exists. duplicate key value violates unique constraint "core_repositoryversion_repository_id_number_3c54ce50_uniq" DETAIL: Key (repository_id, number)=(8483dc67-8401-47ba-bb80-203f5a9c0429, 2) already exists. Workaround provided in article https://access.redhat.com/solutions/6718181 solves this by: 1. Stop all but 1 worker on the affected Capsule servers: # for i in {2..8} ; do systemctl stop pulpcore-worker@${i}; done 2. Verify all but 1 worker is stopped: # for i in {1..8} ; do systemctl status pulpcore-worker@${i} | grep Active; done 3. After that trigger an Optimized Capsule sync against the affected Capsules.
The Pulp upstream bug status is at closed. Updating the external tracker on this bug.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days