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.
DescriptionVedashree Deshpande
2022-06-13 06:43:47 UTC
Description of problem:
When publishing new CV version, task fails with error from $subject
Errors:
duplicate key value violates unique constraint "core_repositorycontent_repository_id_content_id_fb06c181_uniq"
DETAIL: Key (repository_id, content_id, version_added_id)=(ea9a371f-a0d0-49fb-8015-e8ff0d7386ec, a35a6e2e-6322-4df5-bacf-c08c31cdb223, 0071580e-9146-4d9f-a9c5-15088dab5594) already exists.
duplicate key value violates unique constraint "core_repositorycontent_repository_id_content_id_fb06c181_uniq"
DETAIL: Key (repository_id, content_id, version_added_id)=(81dc2b7a-ede1-4f9f-a73e-43e401456b11, 12f82b48-86bb-459d-b012-2b7899b8cafd, 0d4a504b-0655-4315-ab0b-28fc6d176686) already exists.
Version-Release number of selected component (if applicable):
satellite-6.10.6-1.el7sat.noarch
satellite-installer-6.10.0.7-1.el7sat.noarch
satellite-cli-6.10.6-1.el7sat.noarch
satellite-common-6.10.6-1.el7sat.noarch
satellite-maintain-0.0.1-1.el7sat.noarch
How reproducible:
Steps to Reproduce:
Steps:
1) Create a content view and attach "Red Hat Satellite Tools 6.10 for RHEL 7 Server RPMs x86_64" repo.
2) Create a package include filter.
3) In the package filter:
a) Add 2 rules to include 'foreman-cli' and 'katello-agent' rpms.
4) Publish the content view. CV version 1.0 should have the following 2 rpms:
- foreman-cli
- katello-agent
5) Amend the package filter:
a) Add 1 rule to include 'katello-host-tools' rpm.
6) Publish the content view again. CV version 2.0 should have the following 3 rpms:
- foreman-cli
- katello-agent
- katello-host-tools
7) Amend the package filter:
a) Remove 2 rules that included 'foreman-cli' and 'katello-agent'.
b) Add 1 rule to include 'katello-host-tools-fact-plugin' rpm.
8) Publish the content view again. CV version 3.0 should have the following 2 rpms:
- katello-host-tools
- katello-host-tools-fact-plugin
9) Amend the package filter:
a) Add 2 rules to include 'foreman-cli' and 'katello-agent' rpms.
10) Publish the content view again. CV version 4.0 should have the following 4 rpms:
- foreman-cli
- katello-agent
- katello-host-tools
- katello-host-tools-fact-plugin
11) Manually trigger a clean orphan task. Wait until the task is finished in Web UI -> Monitor -> Task page.
foreman-rake katello:delete_orphaned_content
12) Amend the package filter:
a) Remove 2 rules that included 'foreman-cli' and 'katello-agent'.
13) Tail the /var/log/messages file
tail -f /var/log/messages
14) Publish the content view again.
I'm 99% certain this is a dup of an existing BZ that was fixed long ago, but I'm super busy right now so I don't particularly want to go find it. 6.10 is EOL and missing tooooons of bugfixes.