Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionVladimír Sedmík
2022-11-14 21:47:51 UTC
Description of problem:
Assume we have a Capsule which is assigned with Library and one another LCE. When we create a new CV with some repo and publish and promote it to the LCE, two sync tasks are triggered for each environment, but one of them fails due to duplicity error.
This might be a corner case worthless of any attention, but since we allow users to publish and promote CVs at the same time via WebUI, it seems to be not so difficult to hit.
Version-Release number of selected component (if applicable):
6.12.0
6.11.4
How reproducible:
always
Steps to Reproduce:
1) have a fresh SAT and CAPS (on_demand, no LCE added yet), create an organization, upload manifest
2) enable some mid-size repo (i.e. rhel-7-server-kickstart) and sync it
3) create new LCE, add it to the capsule together with the Library
4) create new CV, add the repo from 2), publish and promote it to the LCE from 3) -> two capsule sync tasks are triggered, one for Library and one for the new LCE. The first task succeeds, the second one fails.
Actual results:
Task fails with error:
duplicate key value violates unique constraint "core_repositoryversion_repository_id_number_3c54ce50_uniq"
DETAIL: Key (repository_id, number)=(fc310174-5f54-4ccc-8495-15f4b1de55a1, 1) already exists.
Could not lookup a publication_href for repo 4
Expected results:
Both tasks should succeed.