I’m using katello 3.17 (fresh install) and I can’t synchronize rhel-7-server-rpms. The synchronization stops with message “Sync incomplete” and the following exception:
“duplicate key value violates unique constraint “core_repositoryversion_repository_id_number_3c54ce50_uniq”\n” +
“DETAIL: Key (repository_id, number)=(50ad5057-68a1-4067-a0cd-50855cd0f1e9, 2) already exists.\n”},
It was working before. No other repos were added. It suddenly stopped synchronizing. Is there a way to fix it (e.g. cleanup database) or is it a bug?
Katello 3.18RC1 includes this patch which partially fixes the issue:
02:44PM - 27 Oct 20 UTC
The error still occurs but the repo successfully synchronized upon retry.
I believe I ran into the same error and posted comment here:
I believe i just ran into this same error after upgrading from 3.16 to 3.17:
Katello::Errors::Pulp3Error: duplicate key value violates unique constraint "core_repositorycontent_repository_id_content_id_df902e11_uniq"
DETAIL: Key (repository_id, content_id, version_removed_id)=(5cf832a8-c96a-4336-94f2-1617e2f6f3fa, 0b09dd09-de5e-45a4-9807-61961c29b685, 6f8416a0-8cc2-4a85-b458-5634cad2a6d9) already exists.
I reviewed the github commit and tried to manually apply fix, but got a pulp 503 error, s…
However, after manually apply the fix, and then trying publish a content view Version, im seeing a “Pulp 503” error which does not allow the Version to be published. Did you run into any errors after applying fix? Or did it work smoothly for you?
I have also tried to apply the patch manually. It did not work (can’t remember the error code). There are only few hosts registered to katello so it was easy to just install v3.18 from scratch.
I’m having the same issues. I guess I’ll have to wait until 3.18 is released.